same endpoint addresses with spooling -> overlapping spool names cause spool issues about carbon-relay-ng HOT 9 CLOSED

+1

from carbon-relay-ng.

I am seeing this same issue. You mention that the short term solution is to "name them better", can you expand on that? Would I need to use different ports for each or maybe different names in /etc/hosts?

from carbon-relay-ng.

yes, the workaround is making sure that all your combinations of tcp-addr:port of routes are unique, because that's what's used to generate the spool filenames.

from carbon-relay-ng.

Hi @Dieterbe , is there is bugfix for spooling issue in 0.8 version?

from carbon-relay-ng.

no sorry

from carbon-relay-ng.

+1

from carbon-relay-ng.

hey @Dieterbe, what do you think the chances are that #258 would be looked at / merged in to a new release ? I have forked the repo built carbon and have tested locally in our environments. Our issues was that without this fix we had to use regex's instead of a bunch of different routes with the same destination using prefix's. This caused a significantly large performance hit. With these changes we can both spool, and not take that performance hit...

from carbon-relay-ng.

your pr looks pretty good. with a bit more followup I think we can merge your fix.

from carbon-relay-ng.

ok folks, @scrichar made a nice PR that includes the routeName into the key for the destination. so now spool files, metrics, and log entries are all unique instead of colliding! just choose an appropriate route name :) thanks @scrichar !

from carbon-relay-ng.