Fix ES bulk processor commit timeout #3696
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.
What changed?
Increased default number of bulk processor workers from 1 to 2. Rationale: it should help with commit latency during traffic spikes and with "wait add" latency.This goes to Increase default number of Elasticsearch bulk processor workers to 2 #3738 instead.elasticsearch_bulk_processor_queued_requests
metric is emitted. It now shows number of pending requests after current bulk is processed.Why?
Fixing bugs, improving overall ES write latency.
How did you test it?
Existing tests.
Potential risks
No risks.
Is hotfix candidate?
Yes.