High distributor % for single node in monolith deploy. #9393
Unanswered
jzakhar
asked this question in
Help and support
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We've have 3 Mimir nodes setup for sometime now and recently during a normal update -> rolling reboot one of our ops engineers noticed that the distributor ring was being pinned to one node.
Instance ID | Availability Zone | State | Address | Registered At | Last Heartbeat | Tokens | Ownership | Actionsinstance1.domain.com | | ACTIVE | 1.1.1.185:9095 | 2024-09-17T14:01:24Z | 14.134s ago (17:19:39) | 1 | 3.84% | Forget
instance2.domain.com | | ACTIVE | 1.1.1.194:9095 | 2024-09-17T14:07:27Z | 11.135s ago (17:19:42) | 1 | 0.77% | Forget
instance3.domain.com | | ACTIVE | 1.1.1.140:9095 | 2024-09-17T14:11:14Z | 9.135s ago (17:19:44) | 1 | 95.4% | Forget
That third instance is 95%, if we reload the process that 95% moves to somewhere else. I also see that there is only 1 token available.
The config we run is :
Do we need to add num_tokens under the ring stanza for the distributer like the ingester has ?
The ingester defaults + our changes come out looking like this :
Which has num_tokens while the distributor does not.
anyway, any help is much appreciated.
TYIA
Beta Was this translation helpful? Give feedback.
All reactions