Integrating into an established environment. about carbon-c-relay HOT 6 CLOSED

nope, carbon-c-relay doesn't support the "target" or whatever it is called (the ":a")

from carbon-c-relay.

Just remove :a from DESTINATIONS -
DESTINATIONS = 10.0.0.100:2120,10.0.0.200:2120,10.0.0.300:2120,10.0.0.400:2120
will work in compatible way. If you are using it on localhost you can use IP 127.0.0.X then.

from carbon-c-relay.

I see what you mean now. Unfortunately removing the targets that would change the hashing of the current relays so I'd have the same issue of whisper duplication. Looks like I'll have to merge whispers either way. Thanks for the clarification.

from carbon-c-relay.

Unless it is really important for you, I'd rather not implement it. If you're /only/ using ":a", you could consider patching consistent-hash.c to replace "(None)" with "a" in the carbon_ch construction.

from carbon-c-relay.

@grobian thanks for the suggestion it worked perfectly. If anyone else needs this behaviour line 127 of consistant-hash.c gets modified as below.

snprintf(buf, sizeof(buf), "('%s', None):%d", server_ip(s), i);
becomes
snprintf(buf, sizeof(buf), "('%s', 'a'):%d", server_ip(s), i);

from carbon-c-relay.

@gdavis33,
yep, but only when you are using same instance ':a' across all relays. :)

from carbon-c-relay.