Vladimir Smirnov

So to clarify: you are currently using go-carbon as a backend and there you get wrong data, but once you switch to carbon-clickhouse it is correct? In that case, could...

Would graphite-web's behavior change if you point to carbonserver, instead of reading wsp files directly? According to the docs for the image, you can do that by setting `GRAPHITE_CLUSTER_SERVERS="127.0.0.1:8000"` (that's...

And by any chance, is this a single docker container or you have multiple go-carbon docker containers in carbonapi?

I've tried to reproduce your issue with files you've provided, but also no luck: 1. graphite-web (current master) with CLUSTER_SERVER - returns exactly same data 2. graphite-web (current master) pointed...

Example for the test: https://github.com/go-graphite/carbonapi/blob/main/cmd/mockbackend/testcases/i484/i484.yaml Structure: `version: "v1"` - config version in case I'll want to change something in future. **Query part of the test** `test` - main section that...

It seems you are right, there is a behavioral change in terms of "sendGlobsAsIs" since 0.10. Back then all requests were sent in parallel, however now after "split" they are...

Ok, I think I found a place which was parallel in older versions of carbonapi but now it's not. I've added a flag that should enable old behavior (also if...

I would suggest to try something like: ``` upstreams: buckets: 10 timeouts: find: "300s" global: "300s" afterStarted: "120s" connect: "500ms" # alwaysSendGlobsAsIs: true maxBatchSize: 100 concurrencyLimitPerServer: 1000 concurrencyLimit: 1000 concurency:...

0.15.4 should have a fix to make errors more useful. What worries me is that the error happens after 1.3 second, which is way below all timeout limits. Is there...

@reyjrar Also for you I suggest to set `doMultipleRequestsIfSplit: true` as it might be important when you have a huge request that is being split to a series of smaller...