← Back to team overview

graphite-dev team mailing list archive

Re: [Question #175552]: stats data started to be much behind after updating to 0.9.9

 

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

    Status: Open => Answered

chrismd proposed the following answer:
Sorry I let your question expire, I've been on hiatus for a couple weeks
but I'm back now. This is the second time I've heard of the second issue
you mention, (cache query for "ounters...") where the first character of
the metric name is chopped off. I've never been able to reproduce it
myself but one other user has reported it, long before 0.9.9 though. I
suspect this is due to mixed versions of the code, can you reinstall and
use 'setup.py install --force'? If you don't specify --force and it is
an upgrade then often times some files don't get overwritten. I have no
idea why distutils sometimes does not update files without --force but
I've experienced this with other python apps as well.

The exception in datalib.py is a cache query timing out. What does your
carbon-cache daemon's cpu usage look like? If it's too high this can
happen, also you can increase the cache query timeout in
local_settings.py by setting CARBONLINK_TIMEOUT to something more than
1.0 (the default), the unit is seconds.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.