Sean Hanson
Sean Hanson
I just meant doing a Depth-first search to try to find a leaf within the time boundaries could be very expensive for a large enough index.
Is this still being worked on?
I believe @robert-milan is doing work on this.
Perhaps `groupByTags` should be "smarter" in building the key to prevent this issue instead of relying on string encoding/parsing?
> @shanson7 do you feel the following 2 tests adequately cover the problem Maybe? I'd like to see those tests using the `name` tag and a case using another tag...
I'm seeing these fairly frequently. Any idea what the issue is?
I deployed a “silent node” (carbon in, partition 9999) and added some debug statements It turns out the buffers are coming back as nil `2018/05/09 21:05:26 [dataprocessor.go:223 func1()] [E] DEBUG...
I think this is ccache corruption. For this particular repro request it was always the same instance that was breaking things. I sent a ccache/delete request and now the error...
Sorry, to clarify: 1. The main issue of `msgp: too few bytes left to read object` is coming from [here](https://github.com/grafana/metrictank/blob/a19124e/api/dataprocessor.go#L221). This happens when the request to the peer is canceled...
We had another customer complaining about this. They publish forecasted data every Sunday for the next week. Because of the compressed publishing window, the `lastUpdate` is roughly 7 days behind....