graphite-dev team mailing list archive

[Will <question285063@xxxxxxxxxxxxxxxxxxxxx>]

Question #285063 on Graphite changed:
https://answers.launchpad.net/graphite/+question/285063

Will gave more information on the question:
I removed the g and h instances of carbon-cache and things seem to be
better as far as memory errors are concerned.

However, I'm still seeing inflated cache sizes for Carbon and queued
metrics for Carbon-C-Relay. Also this keeps happening in the
Carbon-C-Relay logs:

=====

[2016-02-22 10:23:37] (ERR) failed to write() to 10.201.12.199:2413: uncomplete write
[2016-02-22 10:23:37] (ERR) failed to write() to 10.201.12.199:2013: uncomplete write
[2016-02-22 10:23:37] (ERR) failed to write() to 10.201.12.199:2513: uncomplete write
[2016-02-22 10:23:37] (ERR) server 10.201.12.199:2413: OK
[2016-02-22 10:23:37] (ERR) server 10.201.12.199:2013: OK
[2016-02-22 10:23:37] (ERR) server 10.201.12.199:2513: OK

=====

This recovers for a minute or two if I forcefully kill and restart the
Carbon-Cache procs, but quickly slips back into erroneous behavior. I
have metrics with holes or delays in the data as a result.

-- 
You received this question notification because your team graphite-dev
is an answer contact for Graphite.