Details
Description
Incremental Elasticsearch index updates, such as those triggered by component and asset entity events, currently use the standard put and delete API. When a massive insert of assets occurs this could cause index updates to fail for the same reason as NEXUS-12520
To get the same benefits as NEXUS-12520 (automatic retries, etc.) we should also use the bulk API for incremental updates.
Attachments
Issue Links
- fixes
-
NEXUS-13466 SearchServiceImpl ERROR Elasticsearch index thread pool is overloaded message may appear in nexus.log
-
- Closed
-