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

Provide a tool to analyze the content of the default WorkManager queue

    Details

    • Tags:
    • Upgrade notes:
      Hide

      There is now a way to get statistics on the type of Works that are processed in the default WorkManager queue.

       ./bin/stream.sh workCat --chronicle /var/lib/nuxeo/stream/ -l work/default -n 10 --codec avro
      ...
      pos,class,fullname,category,name
      work-default-01:+79907866542080,ListenerWork,org.nuxeo.ecm.core.event.impl.AsyncEventExecutor.ListenerWork,pictureViewsGenerationListener,ListenerWork(Listener...
      
      Show
      There is now a way to get statistics on the type of Works that are processed in the default WorkManager queue. ./bin/stream.sh workCat --chronicle / var /lib/nuxeo/stream/ -l work/ default -n 10 --codec avro ... pos, class, fullname,category,name work- default -01:+79907866542080,ListenerWork,org.nuxeo.ecm.core.event.impl.AsyncEventExecutor.ListenerWork,pictureViewsGenerationListener,ListenerWork(Listener...
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #23
    • Story Points:
      2

      Description

      The WorkManager default queue contains different types of Works.

      When there is a performance issue represented by a lag on this queue, it is hard to understand what kind of processing is implied.

      The idea is to dump the content of the queue and provide raw data that can be used for analytics, it should display:

      • Work class
      • Work Category
      • Work name

      This will help to pinpoint which asynchronous listener is overly used and decide to create a dedicated queue and get access to WorkManager metrics.

      This is only feasible for the StreamWorkManager where Works are persisted into a stream (and not destroyed after execution),
      this can be done by adding a new command to the stream.sh tool.

        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 - 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.