We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64847

Make jira cache flush events non-blocking

XMLWordPrintable

    • 1
    • 6
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      If in some case when many cache flush events are generated (see JRA-64839) all those events are blocking events. During that time cache is not usable and if this is hot cache that degrades JIRA performance.

      Following sequence will happen:

      1. Cache flush events generated in loop - Thread1
      2. Cache will be flushed - Thread1
        • If this is a hot cache, there will be attempt to populate it - Thread2
        • Thread will try to flush cache but will be blocked - Thread1
      3. Cache population is done - Thread2
      4. Cache will be flushed - Thread1
      5. Repeat until all cache events are done.

      Suggested Solution

      Make jira cache flush events non-blocking

      JRASERVER-67019 makes cache flush less coupled for DC.

      Workaround

      None

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-64847

            Make jira cache flush events non-blocking

            XMLWordPrintable

              • 1
              • 6
              • 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.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

                Problem Definition

                If in some case when many cache flush events are generated (see JRA-64839) all those events are blocking events. During that time cache is not usable and if this is hot cache that degrades JIRA performance.

                Following sequence will happen:

                1. Cache flush events generated in loop - Thread1
                2. Cache will be flushed - Thread1
                  • If this is a hot cache, there will be attempt to populate it - Thread2
                  • Thread will try to flush cache but will be blocked - Thread1
                3. Cache population is done - Thread2
                4. Cache will be flushed - Thread1
                5. Repeat until all cache events are done.

                Suggested Solution

                Make jira cache flush events non-blocking

                JRASERVER-67019 makes cache flush less coupled for DC.

                Workaround

                None

                        izinoviev Ilya Zinoviev (Inactive)
                        ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
                        Votes:
                        17 Vote for this issue
                        Watchers:
                        23 Start watching this issue

                          Created:
                          Updated:

                            izinoviev Ilya Zinoviev (Inactive)
                            ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
                            Votes:
                            17 Vote for this issue
                            Watchers:
                            23 Start watching this issue

                              Created:
                              Updated: