Uploaded image for project: 'Jira Service Management Server and Data Center'
  1. Jira Service Management Server and Data Center
  2. JSDSERVER-6490

Opening Service Desk Queue will send many Cache replication requests for Queue Count

    XMLWordPrintable

Details

    Description

      Issue Summary

      Opening /projects/<project-key>/queues will send Cache replication requests of each queue separately. This happens on every load of the page and unique per user.

      Environment

      • Data Center

      Steps to Reproduce

      1. Create a SAMPLE Service Desk project
      2. Enable TRACE on com.atlassian.jira.cluster.distribution.localq
      3. Load the Service Desk Queue

      Expected Results

      A single PUT localQ action is being made per user.

      Actual Results

      Multiple PUT localQ actions were made. Total amount of PUT trace is equivalent to the number of Queue available in the project

      2019-07-26 11:01:50,589 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 1
      2019-07-26 11:01:50,591 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,593 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,597 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,599 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,602 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,605 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,608 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,611 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,614 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,616 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,619 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,621 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,623 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,625 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,629 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,631 localq-reader-5 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: PUT to node: node1 in timeInMillis: 0
      2019-07-26 11:01:50,642 localq-reader-1 TRACE      [c.a.j.c.d.localq.rmi.LocalQCacheOpRMISender] Send localQCacheOp.action: REMOVE to node: node1 in timeInMillis: 0

      Notes

      • Reloading of the page will refresh the cache and replicate
      • Switching between queue in the same page will refresh the cache and replicate
      • Enabling cache-count mechanism from JSDSERVER-4897 reduces the cache refresh to be every 2 minutes on cache expiry

      Workaround

      To reduce or stop the cache replication made by the Service Desk queue, follow the steps in JSDSERVER-4897

      Attachments

        Issue Links

          Activity

            People

              jxu2@atlassian.com Sam Xu
              znoorsazali Zul NS [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync