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

Support configuration of node locality #2199

Open
Tracked by #2198
tillrohrmann opened this issue Nov 1, 2024 · 0 comments
Open
Tracked by #2198

Support configuration of node locality #2199

tillrohrmann opened this issue Nov 1, 2024 · 0 comments

Comments

@tillrohrmann
Copy link
Contributor

tillrohrmann commented Nov 1, 2024

In order to enable locality-aware logs configuration, we need to support configuring the locality for nodes. Based on this information, the cluster controller and other components can make decisions on where to place loglet replicas and which nodes to replicate data to.

One idea could be to allow users to specify a set of key value pairs at startup of the form --locality=region=us-west-1,zone=sf,rack=1 which describe the location of the node. This information could be recorded in the NodesConfiguration to make it accessible to the various components that need this information. This approach would also allow to specify other labels that could be considered when placing loglets. If the locality value starts with the most inclusive scope (region, then az, then something else), then we could pick nodes such that we first try to find nodes with different values for the most inclusive scope, then continue with the second most and so on (looking for nodes with different prefix values and expanding the prefix if needed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant