Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distribute object authority by HOST name #10157

Open
Al2Klimov opened this issue Sep 17, 2024 · 0 comments · May be fixed by #10161
Open

Distribute object authority by HOST name #10157

Al2Klimov opened this issue Sep 17, 2024 · 0 comments · May be fixed by #10161
Assignees
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request ref/IP

Comments

@Al2Klimov
Copy link
Member

Currently, we hash the full name of each object and decide by % 2 which endpoint is responsible. This can spread relatives like host->service, checkable->downtime/notification/... apart, so that theoretically each thing, eg. trigger a notification, only happens after a cluster message makes if from node A to B. Greetings to lags and message loss!

If ApiListener::UpdateObjectAuthority() would hash not the whole name, but only the part up to the first !, everything under a host would be processed on the same node, reducing latency and making stuff more robust.

Idea (c) @julianbrost
ref/IP/52571

@Al2Klimov Al2Klimov added enhancement New feature or request area/distributed Distributed monitoring (master, satellites, clients) ref/IP labels Sep 17, 2024
@Al2Klimov Al2Klimov self-assigned this Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/distributed Distributed monitoring (master, satellites, clients) enhancement New feature or request ref/IP
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant