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

Possible work pool termination with StreamWorkManager

    Details

    • Release Notes Summary:
      Work pool terminations are better handled with StreamWorkManager.
    • Backlog priority:
      600
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #18
    • Story Points:
      3

      Description

      When using the StreamWorkManager, It seems there is a code path where failures can lead to a termination of the Work Queue thread pool in a silent way (without tracing errors).

      This has been observed with indexing Work (ScrollingIndexingWorker) that run a MongoDB query which timeouts (SocketTimeout). The thread that runs the Work as a computation terminates without tracing the error and the record is re-assigned on other threads, where the same behavior is seen until there are no more indexing threads in the cluster.

      It is not clear if work in failure are put in the DLQ stream.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 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, 3 hours
                  1d 3h

                    PagerDuty

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