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

As a Jira Admin I want to know Inter-node connection status and latency

XMLWordPrintable

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

      Problem Definition

      It's not easy to understand and troubleshoot if Jira can connect to other nodes in the cluster.

      Suggested Solution

      Create a connection state metric for every pair of nodes. In addition to that, measure the latency of communication between nodes.
      This metric monitors the time to send cache invalidation messages to other nodes. It’s based on real traffic and represents the current status and performance of the Cache replication subsystem.

      Workaround

      None

            [JRASERVER-76230] As a Jira Admin I want to know Inter-node connection status and latency

            Kannan Pillai made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1007104 ]
            Alexander Artemenko made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 967514 ]
            Alexander Artemenko made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 965034 ]
            Krzysztof Dubanowicz made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 845980 ]
            Krzysztof Dubanowicz made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 845980 ]
            Andriy Yakovlev [Atlassian] made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 806347 ]
            Andriy Yakovlev [Atlassian] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. Problem Definition
            It's not easy to understand and troubleshoot if Jira can connect to the nodes in the cluster.

            h3. Suggested Solution
            Create a connection state metric for every pair of nodes. In addition to that, measure the latency of communication between nodes.
            This metric monitors the time to send cache invalidation messages to other nodes. It’s based on real traffic and represents the current status and performance of the Cache replication subsystem.

            h3. Workaround
            None             		New: h3. Problem Definition
            It's not easy to understand and troubleshoot if Jira can connect to other nodes in the cluster.

            h3. Suggested Solution
            Create a connection state metric for every pair of nodes. In addition to that, measure the latency of communication between nodes.
            This metric monitors the time to send cache invalidation messages to other nodes. It’s based on real traffic and represents the current status and performance of the Cache replication subsystem.

            h3. Workaround
            None
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. Problem Definition
            TBD

            h3. Suggested Solution
            TBD

            h3. Workaround
            None             		New: h3. Problem Definition
            It's not easy to understand and troubleshoot if Jira can connect to the nodes in the cluster.

            h3. Suggested Solution
            Create a connection state metric for every pair of nodes. In addition to that, measure the latency of communication between nodes.
            This metric monitors the time to send cache invalidation messages to other nodes. It’s based on real traffic and represents the current status and performance of the Cache replication subsystem.

            h3. Workaround
            None
            Andriy Yakovlev [Atlassian] made changes -
            Component/s Original: Mail Server [ 44490 ]
            Component/s New: Data Center - Other [ 46110 ]

              418cb3cd182b Krzysztof Dubanowicz
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: