You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 14, 2019. It is now read-only.
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.
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.
The text was updated successfully, but these errors were encountered: