Isolating Tenant-Specific Router Ingestor Issues in Shared Hashring #7419
anarcher
started this conversation in
Ideas & Features
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When an issue occurs with a specific tenant's Ingestor, the problem can sometimes propagate from the front-end Router. To isolate the issue, we tried to configure separate Routers for each tenant. However, because the Routers share the same hashring, issues like quorum shortages in a specific tenant's Ingestor become known to the Routers of other tenants. How about making each tenant's Router refer to and update only its own tenant's hashring?
Beta Was this translation helpful? Give feedback.
All reactions