Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-16058

Aggressive locking in JiraCachingPropertySet causes high contention

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Changes added to JiraCachingPropertySet in v3.13 to make the JiraCachingPropertySet thread-safe are probably over-aggressive in their locking policies.
      Reducing the locking for read-only methods that don't update the cache should help reduce lock contention.

      Attachments

        1. threads_after_patch.PNG
          threads_after_patch.PNG
          97 kB
        2. threads_before_patch.PNG
          threads_before_patch.PNG
          81 kB
        3. WEB-INF.zip
          9 kB

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-13843 Race condition in usage of JiraCachingPropertySet

          • Medium - Medium priority issues
          • Closed

          Activity

            People

              mlassau Mark Lassau (Inactive)
              mlassau Mark Lassau (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: