Skip to content
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.

Consider ketama option as well for CH #8

Closed
SEJeff opened this issue Jun 17, 2015 · 1 comment
Closed

Consider ketama option as well for CH #8

SEJeff opened this issue Jun 17, 2015 · 1 comment

Comments

@SEJeff
Copy link

SEJeff commented Jun 17, 2015

Ketama is an alternative to cityhash which is designed to limit the amount of rebalancing when new servers are added / removed from a CH ring.

@vmg
Copy link
Contributor

vmg commented Jun 17, 2015

Hi @SEJeff! Thanks for the pointer! Because of the way Graphite works, the aggregator is never in charge of selecting the way metrics are sharded. Best Practice (TM)(C) when running a graphite cluster is reporting metrics evenly distributed to a set of Carbon Relays. The carbon relays already use consistent hashing because that's part of Graphite's design, so the job of the aggregator is to simply spread out the load evenly -- something which CityHash does really well and much faster than any CH scheme.

Hope that clears it up!

@vmg vmg closed this as completed Jun 17, 2015
vmg pushed a commit that referenced this issue Feb 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants