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

Don't start scroller computation when stream processors are disabled

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.10-HF30
    • Fix Version/s: QualifiedToSchedule
    • Component/s: Bulk

      Description

      Since NXP-29361 (10.10 HF30) it is possible to disable processors on specific nodes using nuxeo.stream.processing.enabled=false.
      In this case all processors including bulk action processors are not started (there are any consumer threads on Kafka) except for the scroller computation.

      We don't want to have this scroller computation started.

      In 10.10 the bulk service is started programmatically (in master it is done using a normal contribution NXP-28357) this explains why this special computation is started anyway and why this is specific to 10.10.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                bdelbosc Benoit Delbosc
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:

                  PagerDuty

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