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

Nodes must persist which bucket in the hashring they belong to #172

Open
mattbostock opened this issue Oct 29, 2017 · 0 comments
Open

Nodes must persist which bucket in the hashring they belong to #172

mattbostock opened this issue Oct 29, 2017 · 0 comments
Assignees
Labels

Comments

@mattbostock
Copy link
Owner

mattbostock commented Oct 29, 2017

Using Jumphash, nodes are represented by buckets.

In order to minimise the amount of data that moves when nodes are added or removed, nodes must remember which bucket they belong to and use that same bucket when they reconnect to the cluster.

Found during the implementation of #149.

This limitation is mentioned in the abstract for Jumphash:

Its main limitation is that the buckets must be numbered sequentially, which makes it
more suitable for data storage applications than for distributed web caching.

...the consequences of which were not clear to me when deciding on #27.

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

No branches or pull requests

1 participant