Versions Compared

Old Version 4

changes.mady.by.user Stanley Neychev

Saved on

compared with

New Version 5

changes.mady.by.user Rosen Marinkov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

On this page:

Table of Contents
Tip

Configuration Manager for Jira (CMJ) is compatible with Jira Data Center.

Note

Don't use the ClearCacheEvent option

As of Configuration Manager for Jira 6.13.3, the option to “Send ClearCacheEvent to clear Jira's internal caches after deployment" in General Settings has been removed. Additionally, the Clear Caches button in Advanced Utilities has also been removed.

That's because triggering them may lead to issues within your Jira instance. So, if you're currently using an older version, DO NOT USE the ClearCacheEvent option or the Clear Caches button.

What is the effect of CMJ operations on Jira Data Center cluster performance?

Jira Data Center allows you to run a cluster of multiple Jira nodes, providing a stable performance under high load. The CMJ operations (snapshot creation, deployment, integrity check, etc.) always run on a single node. This is the node where the user is currently logged in currently and starts the operation from.

Running CMJ operations on a single node ensures that your Jira performance across all other nodes remains stable and no slowdowns in response time occur. Your Jira performance will be affected only on the node where the CMJ operation is running.

...

Don’t use the ClearCacheEvent option

As of Configuration Manager for Jira 6.13.3, the option to “Send ClearCacheEvent to clear Jira's internal caches after deployment” in General Settings has been removed. Additionally, the Clear Caches button in Advanced Utilities has also been removed.

...

How to deal with big snapshot deployments to optimize performance?

The more projects, customized configurations, and issues a snapshot contains, the larger it becomes. Deploying huge snapshots on big Data Center clusters will most likely lead to very slow and problematic deployments. This is due to the number of changes and comparisons CMJ has to make during the deployment, as well as the cache re-indexing that needs to occur after the deployment.

To better deal with heavy deployments, we advise you to create a separate node dedicated to these tasks. Ensure it’s taken off of the load balancer and that it has increased system resources (processor, memory, etc.) to handle those big deployments. By being off of the load balancer, the node won't be slowed down by client requests, and thus, its performance will be much better. Atlassian recommends a similar approach for reducing cluster downtime.

Tip

Best practices for adding a dedicated deployment node

1. Add a new node to your cluster without adding it to the load balancer. Let's call this your deployment node. This way, you'll have a dedicated node for heavy deployments and re-indexes that's fast and reliable without disrupting your workflow. This deployment approach works with any Data Center instance - non-clustered and clustered - regardless of the number of nodes you currently have.

2. Give the deployment node enhanced system resources. Also, consider turning off CMJ’s cache re-index option, which usually triggers immediately after a deployment. This way, you can finish up your deployment, and when everything has been correctly deployed, you can manually initiate a full Jira re-index for the node.

3. Deactivate the deployment node after nodes synchronization is complete. After the successful deployment, all the deployed data will automatically be synced up with your main node/s. After all nodes have synced up the data, you can deactivate the deployment node until you need to make a large snapshot deployment again.