Skip to content

SegmentAllocator: counter ids collide → identical balancer counters #327

Description

@kemsta

Multiple balancer services report identical packets/bytes:

balancer0 91.210.70.0 tcp 80 … 858705 970484997
balancer0 195.242.0.3 tcp 80 … 858705 970484997
balancer0 195.242.0.6 tcp 443 … 858705 970484997

yanet-cli counters stat shows inconsistent allocator state:

size: 4, used blocks: 0, busy blocks: 2, used segments: 2358
Errors external: 149, internal: 6818

used_segments=2358 exceeds the maximum busy_blocks * (BlockSize/size) = 2*1024 = 2048
It seems impossible in a healthy allocator. Errors internal grows over time.

yanet-cli dontdoit podumoi dataplane counter 0 4 returns exactly those 858705/970484997 values, confirming that affected services all share counters[0..3].

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions