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

Add an option to disable WorkManager processing

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 9.10
    • Fix Version/s: 11.1, 2021.0
    • Component/s: Events / Works
    • Release Notes Summary:
      You can now use nuxeo.work.processing.enabled=false to disable WorkManager processing
    • Sprint:
      nxcore 11.1.2
    • Story Points:
      2

      Description

      Defining Nuxeo node that schedules async works but doesn't process them is useful to separate load and scale.

      On the WorkQueueDescriptor there is a flag to enable the queue and a flag to enable/disable the processing.

      For instance to disable all async processing for a Nuxeo node we can do:

        <extension target="org.nuxeo.ecm.core.work.service" point="queues">
          <queue id="*" processing="false"/>
        </extension>
      

      But you need to put the right requirements so the contribution is the last one, this is not always possible and it would be better to have an option in the configuration service for this.

      This should work for both WorkManager implementation (default and stream).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h

                    PagerDuty

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