Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20977

The development status summary panel is timing out when under heavy load even if data is available

XMLWordPrintable

      Issue Summary

      The development status summary panel is timing out when under heavy load even if data is available

      Steps to Reproduce

      1. Connect a DVCS integration (Bitbucket, Gitlab or Github) with a linked issue
      2. Open 30+ tabs that auto-refresh (can use http://www.dummysoftware.com/easy-auto-refresh/?ref=chrome for this)
      3. In a separate browser open that same issue and refresh a few times until you see an error message about timeout or failure to load under the dev panel:

      The following exception is thrown into logs:

      2021-06-09 15:02:19,323+0100 http-nio-2990-exec-218 WARN admin 902x36691x25 eeeqnf 127.0.0.1 /rest/dev-status/1.0/issue/summary [c.a.j.p.devstatus.provider.DefaultCoordinator] GitLab (timeout after 5000ms, cached data returned)
      

      There’s only 15 threads max that can fetch DVCS data at a time so this is causing contention:

         this.dvcsDataFetcherExecutor = ThreadPool.builder()
                      .name("dvcs." + dvcsType())
                      .maxThreads(15)
                      .boundedQueue(QUEUE_SIZE)
                      .build();
      

      and the call to timeout. Note that increasing the timeout will not help here.

      Expected Results

      DVCS data related to the issue should load in the Dev Panel.

      Actual Results

      Data is not loaded into the dev panel which should return either the cached existing data or the new one stored into DB after soft or hard sync.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              7e8b5dfc9af0 Nitesh Giri
              tmarchionni@atlassian.com Tiziana Marchionni
              Votes:
              33 Vote for this issue
              Watchers:
              42 Start watching this issue

                Created:
                Updated:
                Resolved: