New question #249502 on Graphite:
https://answers.launchpad.net/graphite/+question/249502


I'm setting up Graphite 0.10 using ceres and megacarbon. (using the latest 
checkout from the git repository)

While aggregating data with sum aggregationMethod using 'ceres-maintenance 
rollup',
CeresNode.read is merging data from multiple slices incorrectly.

Here is repro step.

in my storage-rules.conf
[counter-metrics]
pattern = \.count$
retentions = 1s:10m, 10s:1h, 1m:12h, 10m:30d
aggregation-method = sum

in the ceres node directory,
.ceres-node
{"timeStep": 1, "retentions": [[1, 600], [10, 360], [60, 720], [600, 4320]], 
"xFilesFactor": 0.5, "aggregationMethod": "sum", "retention": "1m:30d"}

After feeding data for about 15 minutes, I have data in 1 second resolution 
only.

<slicecat [email protected]>
[1401395951]    Thu May 29 13:39:11 2014        21.0
[1401395952]    Thu May 29 13:39:12 2014        422.0
[1401395953]    Thu May 29 13:39:13 2014        nan
[1401395954]    Thu May 29 13:39:14 2014        426.0
...
[1401396401]    Thu May 29 13:46:41 2014        397.0
[1401396402]    Thu May 29 13:46:42 2014        420.0
[1401396403]    Thu May 29 13:46:43 2014        415.0
[1401396404]    Thu May 29 13:46:44 2014        409.0
[1401396405]    Thu May 29 13:46:45 2014        296.0

<node-read>
Thu May 29 13:39:11 2014        21.0
Thu May 29 13:39:12 2014        422.0
Thu May 29 13:39:13 2014        None
Thu May 29 13:39:14 2014        426.0
...
Thu May 29 13:46:41 2014        397.0
Thu May 29 13:46:42 2014        420.0
Thu May 29 13:46:43 2014        415.0
Thu May 29 13:46:44 2014        409.0
Thu May 29 13:46:45 2014        296.0
Thu May 29 13:46:46 2014        None

Well matched... good!!!

To aggregate this data to 1 min resolution, run ceres-maintenance rollup.
ceres saves low-resolution data into [email protected] besides 
[email protected].

<slicecat [email protected]>
[1401395950]    Thu May 29 13:39:10 2014        2958.0
[1401395960]    Thu May 29 13:39:20 2014        4036.0
[1401395970]    Thu May 29 13:39:30 2014        4049.0
[1401395980]    Thu May 29 13:39:40 2014        4155.0
[1401395990]    Thu May 29 13:39:50 2014        4138.0
[1401396000]    Thu May 29 13:40:00 2014        4144.0
[1401396010]    Thu May 29 13:40:10 2014        4144.0
[1401396020]    Thu May 29 13:40:20 2014        4023.0
[1401396030]    Thu May 29 13:40:30 2014        4049.0
[1401396040]    Thu May 29 13:40:40 2014        4156.0
[1401396050]    Thu May 29 13:40:50 2014        4163.0
[1401396060]    Thu May 29 13:41:00 2014        4174.0
[1401396070]    Thu May 29 13:41:10 2014        4156.0
[1401396080]    Thu May 29 13:41:20 2014        3924.0
[1401396090]    Thu May 29 13:41:30 2014        4159.0
[1401396100]    Thu May 29 13:41:40 2014        4165.0
[1401396110]    Thu May 29 13:41:50 2014        4171.0
[1401396120]    Thu May 29 13:42:00 2014        4161.0
[1401396130]    Thu May 29 13:42:10 2014        4169.0
[1401396140]    Thu May 29 13:42:20 2014        3932.0
[1401396150]    Thu May 29 13:42:30 2014        4157.0
[1401396160]    Thu May 29 13:42:40 2014        4167.0
[1401396170]    Thu May 29 13:42:50 2014        4141.0
[1401396180]    Thu May 29 13:43:00 2014        4147.0
[1401396190]    Thu May 29 13:43:10 2014        4100.0
[1401396200]    Thu May 29 13:43:20 2014        3857.0
[1401396210]    Thu May 29 13:43:30 2014        4144.0
[1401396220]    Thu May 29 13:43:40 2014        4138.0

Looks good!

<node-read - Completely wrong!!!>
Thu May 29 13:39:10 2014        2958.0
Thu May 29 13:39:11 2014        4036.0
Thu May 29 13:39:12 2014        4049.0
Thu May 29 13:39:13 2014        4155.0
Thu May 29 13:39:14 2014        4138.0
Thu May 29 13:39:15 2014        4144.0
Thu May 29 13:39:16 2014        4144.0
Thu May 29 13:39:17 2014        4023.0
Thu May 29 13:39:18 2014        4049.0
Thu May 29 13:39:19 2014        4156.0
Thu May 29 13:39:20 2014        4163.0
Thu May 29 13:39:21 2014        4174.0
Thu May 29 13:39:22 2014        4156.0
Thu May 29 13:39:23 2014        3924.0
Thu May 29 13:39:24 2014        4159.0
Thu May 29 13:39:25 2014        4165.0
Thu May 29 13:39:26 2014        4171.0
Thu May 29 13:39:27 2014        4161.0
Thu May 29 13:39:28 2014        4169.0
Thu May 29 13:39:29 2014        3932.0
Thu May 29 13:39:30 2014        4157.0
Thu May 29 13:39:31 2014        4167.0
Thu May 29 13:39:32 2014        4141.0
Thu May 29 13:39:33 2014        4147.0
Thu May 29 13:39:34 2014        4100.0
Thu May 29 13:39:35 2014        3857.0
Thu May 29 13:39:36 2014        4144.0
Thu May 29 13:39:37 2014        4138.0
Thu May 29 13:39:38 2014        21.0
Thu May 29 13:39:39 2014        422.0
Thu May 29 13:39:40 2014        None
Thu May 29 13:39:41 2014        426.0
...
Thu May 29 13:47:08 2014        397.0
Thu May 29 13:47:09 2014        420.0
Thu May 29 13:47:10 2014        415.0
Thu May 29 13:47:11 2014        409.0
Thu May 29 13:47:12 2014        296.0
Thu May 29 13:47:13 2014        None
Thu May 29 13:47:14 2014        None
Thu May 29 13:47:15 2014        None
Thu May 29 13:47:16 2014        None
Thu May 29 13:47:17 2014        None
...
None
...
Thu May 29 13:54:41 2014        None
Thu May 29 13:54:42 2014        None
Thu May 29 13:54:43 2014        None
Thu May 29 13:54:44 2014        None
Thu May 29 13:54:45 2014        None

Looks CeresNode.read merge slices with the wrong timestep value.
Graphite-web would display wrong graph of course.

Anyone experienced this problem?


-- 
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     : [email protected]
Unsubscribe : https://launchpad.net/~graphite-dev
More help   : https://help.launchpad.net/ListHelp

Reply via email to