Control Unintended Syncs Between Production and Staging
Exalate now offers enhanced control over your synchronization processes, specifically designed to prevent unintended interactions between your production and staging environments during setup or restarts. This new feature ensures that your cloned staging instances remain isolated from your live production environment until you explicitly activate them.
This feature is currently available for Jira on-premise only.
The Challenge with Cloned Staging Environments
Previously, when cloning a production instance to create a staging environment, synchronization workers would be active by default. This means your sync would always be active by default. This could lead to:
Unintended Syncs: Your staging instance might inadvertently process synchronization requests meant for the production instance.
Data Conflicts: This could result in data corruption, inconsistencies, or unwanted data exchange between your environments.
Introducing Sync Control For Jira On-premise
To address these challenges, Exalate now provides a control mechanism: sync workers are deactivated by default on the production and staging instances and are configured to remain inactive until manually started. This feature helps you prevent accidental synchronization, especially in critical production and staging scenarios.
This means that even if an Exalate node is cloned from a production instance or cluster restart, it will not start synchronizing automatically and you'll need to activate it manually.
How to Activate the Sync Control Feature
This functionality is integrated into the latest Exalate build and does not require additional configuration.
Activation Steps:
Following a cluster restart or the cloning of a production node, an Exalate administrator should proceed to the Exalate console and activate synchronization by clicking the "Activate sync" button.
What Happens if Sync Workers Are Inactive?
Even when sync workers aren't active, Exalate still detects changes that would normally trigger a synchronization. Any issues that would have been synchronized during this inactive period are listed in the Sync Queue. Once you manually activate synchronization by clicking the "Activate sync" button, all issues in the Sync Queue will then be processed.