Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30899

ScrollingIndexingWorker should have its own transaction timeout

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.10-HF63, 2021.18
    • Component/s: Elasticsearch

      Description

      The ScrollingIndexingWorker Work that is listing documents to index can fail during the scroll because of MongoDB time limit:

      MongoExecutionTimeoutException: operation exceeded time limit

      this is because the MongoDB query maxTime is set accordingly to the transaction time to live, and this work is using the default transaction timeout duration which is not enough for a large scrolling.

      The transaction duration should use a big value like 48h (the same value as for the bulk scroller computation).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.