search

jjneely / buckytools

Go implementation of useful tools for dealing with Graphite's Whisper DBs and Carbon hashing
Other
87 stars 21 forks source link

bucky rebalance by removing a node #36

Open ritmas opened 4 years ago

ritmas commented 4 years ago

The way how a cluster is being rebalanced by adding new/empty node is pretty straightforward and clear.

I wanted to ask what is the best flow for rebalancing an existing cluster (replication=1) by removing a node? I tried switch/setup replication=2 (on both carbon-c-relay and buckyd) on running cluster but bucky inconsistent does not show any inconsistency.

jjneely commented 4 years ago

I never got replication > 1 support working in Bucky tools before the client I was working with went in different directions, unfortunately.

To move to a smaller Graphite cluster, I would usually build that smaller cluster and use rebalance to transition to it. But I think the same can be done to just remove a node from the existing cluster. (Watch out if using the Jump hash method as it really only supports removing the last node rather than a node in the middle.)

The usage for rebalance:

bucky rebalance [options] [additional buckyd servers...]

Allows you to specify additional buckyd daemons (graphite storage hosts) that are not in the new hashring and consider those metrics when rebalancing the hashring.