-
Notifications
You must be signed in to change notification settings - Fork 917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix ES bulk processor commit timeout #3696
Fix ES bulk processor commit timeout #3696
Conversation
d0da87b
to
a5aa26e
Compare
261cabf
to
51fcc24
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a couple of nit comments.
p.metricsHandler.Histogram(metrics.ElasticsearchBulkProcessorQueuedRequests.GetMetricName(), metrics.ElasticsearchBulkProcessorBulkSize.GetMetricUnit()). | ||
Record(int64(p.mapToAckFuture.Len() - len(requests))) | ||
Record(int64(p.mapToAckFuture.Len())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this metric supposed to mean? Number of queued requests?
Wouldn't it make more sense to call this after the queue size changes? Like, in bulkAfterAction
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like how many documents are still waiting to be flushed. I like the idea of moving this to bulkAfterAction
.
common/persistence/visibility/store/elasticsearch/visibility_store.go
Outdated
Show resolved
Hide resolved
51659ca
to
59250e2
Compare
66dde25
to
20fc1b9
Compare
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.