Denis Zhdanov

@artb1sh : IIRC carbon-c-relay already included in debian repos - https://packages.debian.org/sid/carbon-c-relay

@mmueller101 : you need to configure some gigantic buffer in relay for that. But I would recommend to use specialized proxy for that - https://github.com/leoleovich/grafsy

Hi @tantra35 It's replicas in the hash ring, not carbon replicas. This code just mimicking Python code from carbon - https://github.com/graphite-project/carbon/blob/9fad18df5731271aab6f5c81d32eddcecdc1a695/lib/carbon/hashing.py#L57 Unfortunately buckytools not supporting replication factor >1, even in...

Hi @rsommer, I'm wondering what's expected behaviour of `bucky inconsistent -s` should be? Report inconsistency on single host only? I'm using `-single` for non-standard rebalance operations, e.g. copy all metrics...

I'm not an author of bucky, just a curious user, was wondering about usecase here. Looks pretty valid to me.

My old fork, from the times when jumphash was not merged into master branch - https://github.com/deniszh/buckytools Planning to migrate to latest version. For 'bucky inconsistent -s' - my version also...

@dcharleston: I did nothing for rebalance , it was just working for me out of the box. I’m not actively using buckytools anymore, but you can check this fork for...

@dcharleston : TBH I completely forgot buckytools code. For me, command above `bucky rebalance -no-delete -w 4 -single host001:4242` just copy all files from to host001 to current host.

I don't think that it will work like this. Usually, people using 2-tier setup in that situation - one relay distribute metrics across servers, another relay on the host itself...

You need to run buckyd on all instances, so e.g. two buckyd on same port on srv1 That's why I said: > I don't think that it will work like...