fix: prevent deadlock in Prometheus chunked streaming #700
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When streaming data from Prometheus with large time ranges (> 1 hour), the StreamRowsChunked function would stall after ~100 rows. This was caused by the bwRows channel (buffer size 100) filling up because processBwRows goroutine was never started.
The issue occurred because StreamRowsChunked creates a datastream with NewDatastreamContext() and pushes rows directly, bypassing Start() which normally starts the processBwRows goroutine.
Changes:
This ensures the bwRows channel is drained, preventing the producer from blocking when the buffer fills up.
Related: #668