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

Adjust the MongoDB query maxTime with transaction timeout

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.10-HF27
    • Fix Version/s: 10.10-HF40, 11.5, 2021.2
    • Component/s: Core MongoDB
    • Release Notes Summary:
      The maximum query execution time on MongoDB side is now aligned with the Nuxeo transaction.
    • Upgrade notes:
      Hide

      The maximum query execution time on MongoDB side is now aligned with the Nuxeo transaction. The configurable maxTime introduced in NXP-29112 is only used when queries are performed outside of a transaction.

      Show
      The maximum query execution time on MongoDB side is now aligned with the Nuxeo transaction. The configurable maxTime introduced in NXP-29112 is only used when queries are performed outside of a transaction.
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #27
    • Story Points:
      5

      Description

      Since NXP-29112 there is a maximum time for MongoDB queries (server-side).

      This prevents to have running eating resources while the client (Nuxeo) has been disconnected.

      NXP-29112 sets a max time to 1h, previously it was unlimited.

      Even if this is configurable this one more thing to align with transaction timeout when long queries are expected.
      For instance, the bulk scroll query that can take hours on a very large repository is supposed to fail now after 1h
      while if the transaction timeout is explicitly set to 2 days.

      The MongoDB maxTime should be set according to the current transaction timeout when a query is part of a transaction.
      Outside of a transaction we can keep the constant max time like in NXP-29112.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day
                  1d

                    PagerDuty

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