Uploaded image for project: 'Sling'
  1. Sling
  2. SLING-8945

ActiveResourceQueue doesn't provide cluster-consistent processing-attempts view

    XMLWordPrintableJSON

    Details

      Description

      [0] enables ActiveResourceQueue (introduced via SLING-8853) to capture processing attempts, but since those are kept in memory the processing-attempts view is not cluster-consistent. Specifically, if a ActiveResourceQueue is introspected, and its Status or its Item Status is requested by an instance that is not processing the ResourceQueue (say, in response to a browser request), the statuses will be returned incorrectly (e.g., a blocked queue will be returned as running since the processing attempts will not be incremented on the instance not processing the queue).

      One way to fix this would be to persist the processing attempts alongside the queue-items in the resource-tree that backs the ResourceQueue.

      [0] https://github.com/apache/sling-org-apache-sling-distribution-core/commit/20f5575af5318c07c31e7623319cf4f1d20258c8

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marett Timothee Maret
                Reporter:
                ashishc Ashish Chopra
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m