Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-20500

A cluster panic should not bring down other nodes

XMLWordPrintable

    • We collect Confluence 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 Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Currently a cluster panic will bring down all nodes.

      For example in a 3 node cluster if one node was to leave the cluster and panic, it would brind down the other two.

      Is this neccessary? Can it only bring down the node that has discovered that something else is updating the database.

            [CONFSERVER-20500] A cluster panic should not bring down other nodes

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3563959 ] New: JAC Suggestion Workflow 3 [ 4322390 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3169905 ] New: JAC Suggestion Workflow 4 [ 3563959 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3025069 ] New: JAC Suggestion Workflow 2 [ 3169905 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2526071 ] New: JAC Suggestion Workflow [ 3025069 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2269409 ] New: Confluence Workflow - Public Facing v4 [ 2526071 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2166197 ] New: Confluence Workflow - Public Facing v3 [ 2269409 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1923418 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2166197 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1755933 ] New: Confluence Workflow - Public Facing v3 [ 1923418 ]
            jonah (Inactive) made changes -
            Description Original: Currently a cluster panic will bring down all nodes.

            For example in a 3 node cluster if one node was to leave the cluster and panic, it would brind down the other two.

            Is this neccessary? Can it only bring down the node that has discovered that something else is updating the database.

            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-20500].
              {panel}

            Currently a cluster panic will bring down all nodes.

            For example in a 3 node cluster if one node was to leave the cluster and panic, it would brind down the other two.

            Is this neccessary? Can it only bring down the node that has discovered that something else is updating the database.

            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-20500 [ CONFCLOUD-20500 ]

              Unassigned Unassigned
              pkamal Partha
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: