Batch CQ writes to avoid timeouts #3517
Merged
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.
Currently continuous query timeouts are causing the server to reject writes, here's how you can replicate it:
start influxdb server
in a second console, run the following ruby script
After a few seconds, the server will crash after the first CQ run and never recover:
The output of the ruby script is:
This pull requests reduces the time needed to run the CQ and avoids timeouts but it - unfortunately - doesn't fix the underlying problem which I traced down to
cluster.PointsWriter
but was unable to solve myself.