strange behavior on the same data points query when giving diffrent interval params

[ju_d]

hi, when I give different intervals for the same query, the Zimsum gives different total sum result:

from 1469064360 to 1469064370, 10 seconds total.
Case 1:

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":257,"1469064363":247,"1469064364":278,"1469064366":204,"1469064368":233,"1469064370":244}}]

the real data points are at :1469064360,1469064363,1469064364,1469064366,1469064368,1469064370 . That's 0,3,4,6,8,10 (relatively)
the total result : 257+247+278+204+233+244=1463


Case 2:    2s-zimsum-zero correct

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:2s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":257.0,"1469064362":247.0,"1469064364":278.0,"1469064366":204.0,"1469064368":233.0,"1469064370":244.0}}]

data points change from 0,3,4,6,8,10 to 0,2,4,6,8,10.
the total result remains 1463.

Case 3:    3s-zimsum-zero, correct

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:3s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":257.0,"1469064363":525.0,"1469064366":437.0,"1469064369":244.0}}]

Case 4:    4s-zimsum-zero ,correct

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:4s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":504.0,"1469064364":482.0,"1469064368":477.0}}]

data points: 0,4,8
the total result remains 1463.

Case 5:    5s-zimsum-zero,wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:5s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":782.0,"1469064365":437.0,"1469064370":757.0}}]

data points: 0,5,10
total result : 782+437+757=1976. why?
the first number :782=257+247+278. the second number: 437=204+233 . but where does the third number 757 come out?
and 782+437=1219, not 1463.

Case 6:    6s-zimsum-zero,correct

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:6s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":782.0,"1469064366":681.0}}]

data points : 0,6
total result 782+681=1463.

Case 7:    7s-zimsum-zero,wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:7s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{}}]

, and nothing returns...

Case 8:    8s-zimsum-zero,wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:8s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":986.0,"1469064368":990.0}}]

Case 9:    9s-zimsum-zero,wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:9s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064366":1194.0}}]

Case 10:    10s-zimsum-zero,wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:10s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":1219.0,"1469064370":1235.0}}]

Case 11:   wrong

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:11s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{}}]

Case 12:  correct

curl 'http://10.195.64.133:4242/api/query?start=1469064360&end=1469064370&m=zimsum:12s-zimsum-zero:key_d13c68f69f40a1a4738c605129ef1cca%7B%7D'
[{"metric":"key_d13c68f69f40a1a4738c605129ef1cca","tags":{},"aggregateTags":["b_uri","z_host"],"dps":{"1469064360":1463.0}}]

I wonder know how exactly the down sample function go, and does "start" and "end" data point including or excluding?

[ManOLamancha]

On Friday, July 22, 2016 at 6:33:05 AM UTC-7, imaor wrote:

I wonder know how exactly the down sample function go, and does "start" and "end" data point including or excluding?

I started https://github.com/OpenTSDB/opentsdb/issues/908 to track this. Could you also let us know which version of TSDB you're using? It may be the earlier downsample code that is affecting this.