• 8
    • 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 Confluence does not support database failover. Specifically, this is the scenario:

      1. Confluence uses Database A.
      2. Database A replicates its content to a contingent Database B.
      3. Database A become unavailable due to some major issue.
      4. Confluence detects the failure of Database A and establishes a connection to Database B.

            [CONFSERVER-8314] Support for Database Failover

            Hi All,

            we also got the same error message, "Every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted.

            Does anyone have a workaround?

            thanks
            Sam

            Sam Koteish added a comment - Hi All, we also got the same error message, "Every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted. Does anyone have a workaround? thanks Sam

            Thanks for raising this one Bijan.

            With the availability of solutions to provide HA for the DB itself, this is not something we want to focus on in the Confluence team.

            Our efforts have instead gone into making sure that you can have a HA version of Confluence itself (with Confluence Data Centre) which you can connect to a HA version of the DB you plan to use.

            John Masson added a comment - Thanks for raising this one Bijan. With the availability of solutions to provide HA for the DB itself, this is not something we want to focus on in the Confluence team. Our efforts have instead gone into making sure that you can have a HA version of Confluence itself (with Confluence Data Centre ) which you can connect to a HA version of the DB you plan to use.

            I'm having also an issue related to SQL Server cluster failover using Availability Groups, which is identical to the previous comment from John Price : "Every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted. We are using the jTDS driver. We're not sure why it doesn't just seamlessly connect to the new, active node, and whether this is the driver or Confluence itself".

            Michel Dermont added a comment - I'm having also an issue related to SQL Server cluster failover using Availability Groups, which is identical to the previous comment from John Price : "Every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted. We are using the jTDS driver. We're not sure why it doesn't just seamlessly connect to the new, active node, and whether this is the driver or Confluence itself".

            John Price added a comment -

            I'm having an issue related to SQL Server cluster failover, which is related but not identical to the need above. I find that every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted. We are using the jTDS driver. We're not sure why it doesn't just seamlessly connect to the new, active node, and whether this is the driver or Confluence itself.

            John Price added a comment - I'm having an issue related to SQL Server cluster failover, which is related but not identical to the need above. I find that every time our SQL Server fails over, Confluence shows the error "Non Clustered Confluence: Database is being updated by another Confluence instance." and must be restarted. We are using the jTDS driver. We're not sure why it doesn't just seamlessly connect to the new, active node, and whether this is the driver or Confluence itself.

            Ditto for MySQL replication.

            Garry Huang added a comment - Ditto for MySQL replication.

            Or this feature.

            1. Primary Datacenter Confluence uses Database A.
            2. Database A used oracle high availability dataguard to Secondary Datacenter Database B.
            3. Confluence Instance in Primary Datacenter and Confluence in Secondary Datacenter are dns'd in a failover situation
            4. If Primary Datacenter is lost - automatically seemlessly fails over to Secondary Confluence Instance.
            5. End User see's no downtime or knows they were directed to the failover environment.

            We've tested this type of setup in our development environment.

            When the Secondary Confluence Instance connects to Database B it sees the connections that are created by Oracle Dataguard - user Public as a cluster and shuts down.

            If there is a way to get the secondary confluence instance to connect to database B, we'd be buying another unlimited commercial license.

            Jeremiah Selander added a comment - Or this feature. 1. Primary Datacenter Confluence uses Database A. 2. Database A used oracle high availability dataguard to Secondary Datacenter Database B. 3. Confluence Instance in Primary Datacenter and Confluence in Secondary Datacenter are dns'd in a failover situation 4. If Primary Datacenter is lost - automatically seemlessly fails over to Secondary Confluence Instance. 5. End User see's no downtime or knows they were directed to the failover environment. We've tested this type of setup in our development environment. When the Secondary Confluence Instance connects to Database B it sees the connections that are created by Oracle Dataguard - user Public as a cluster and shuts down. If there is a way to get the secondary confluence instance to connect to database B, we'd be buying another unlimited commercial license.

              jmasson@atlassian.com John Masson
              2138abefa5c6 Bijan Marjan
              Votes:
              19 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: