Improve implementation of high concurrent elasticsearch operations instead of `RetryOnConflict`
See original GitHub issueIn high concurrent environment, the option RetryOnConflict
for elastic operations is not reliable and there will be errors reported as following:
StackRepository Error occurred incrementing total event occurrences on stack "59cc6fe3bff2a3c6f00d7961". Error: Type: version_conflict_engine_exception Reason: "[stacks][59cc6fe3bff2a3c6f00d7961]: version conflict, current version [8360562] is different than the one provided [8360561]"
The RetryOnConflict has double-edges, although it can improve the success rate, but at the same time it will slow down the elasticsearch updating performance.
more information refer to: https://github.com/exceptionless/Exceptionless/commit/de17ef8ca10d98552e43e16c8d72a990b2419f77
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
What's appropriate value at "retry on conflict"? - Elasticsearch
I want to know an appropriate value of retry on conflict param. ... retrying another index operation instead of stopping after the first....
Read more >Optimistic concurrency control | Elasticsearch Guide [8.9]
When documents are created, updated, or deleted, the new version of the document has to be replicated to other nodes in the cluster....
Read more >Update API | Elasticsearch Guide [8.9]
This operation: Gets the document (collocated with the shard) from the index. Runs the specified script. Indexes the result.
Read more >Configuration | Elasticsearch for Apache Hadoop [7.17]
Operation edit The write operation elasticsearch-hadoop should perform - can be any of: index (default) new data is added while existing data (based...
Read more >API Reference | Elasticsearch JavaScript Client [7.17]
This document contains the entire list of the Elasticsearch API supported by the client, both OSS and commercial. The client is entirely licensed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@niemyjski we have done the performance testing against the old netfx environment, the latest version before you update to netstandard 2.0 When the performance testing completed, we will request a new pr for this. but it will requires a new job to save stack event count separately.
Thanks for the PR!