Question #263940 on Graphite changed: https://answers.launchpad.net/graphite/+question/263940
clohtd posted a new comment: I experienced this problem again. One of my carbon-cache's ran out of memory and was killed by the platform. This caused the carbon-relay to start throwing these twisted errors. I had implemented the fix in https://github.com/datacratic/carbon/commit/2cc77752383288c27c4623a659cd0a76ef95b5a9, changing from state to events, and that changed the message in the relay log. Now I just see the stop/restart messages without the error content. This definitely seems to be approaching an opportunity for improvement. I can't yet intentionally recreate the behavior however yet. I am, however, seeing that if a carbon-cache dies, the relay starts spamming and never recovers when the carbon-cache comes back online. -- You received this question notification because you are a member of graphite-dev, which is an answer contact for Graphite. _______________________________________________ Mailing list: https://launchpad.net/~graphite-dev Post to : graphite-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~graphite-dev More help : https://help.launchpad.net/ListHelp
