Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-13163

Use bulk API for incremental Elasticsearch updates

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 3.3.1, 3.3.2
    • Fix Version/s: 3.4.0
    • Component/s: Search
    • Labels:
    • Story Points:
      2
    • Sprint:
      Platform Team - Sprint 95

      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

          Bug - A problem which impairs or prevents the functions of the product. NEXUS-13466 SearchServiceImpl ERROR Elasticsearch index thread pool is overloaded message may appear in nexus.log

          • Major - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              mcculls Stuart McCulloch
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title