Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Make the active Backbone node in Data Center configurable
Description
In a Data Center environment, all Backbone synchronizations run on one node. An administrator, can't choose right now which node this is. Backbone checks on every node in a periodic manner if still another node is the active Backbone node. If there is no active Backbone node yet or the node went offline, another node will take over.
New Feature An administrator is able to configure a list of nodes which can be the active Backbone nodes. With a list of nodes, a user can still enable that the synchronizations are running if the currently active node dies.
You can activate this by setting a comma separated list of node ids to the system property configuredBackboneNodes.
In a Data Center environment, all Backbone synchronizations run on one node. An administrator, can't choose right now which node this is. Backbone checks on every node in a periodic manner if still another node is the active Backbone node. If there is no active Backbone node yet or the node went offline, another node will take over.
New Feature
An administrator is able to configure a list of nodes which can be the active Backbone nodes. With a list of nodes, a user can still enable that the synchronizations are running if the currently active node dies.
You can activate this by setting a comma separated list of node ids to the system property
configuredBackboneNodes.