...
Migration of large Jira instances between data centers is challenging, especially when trying to complete the migration within a tight window such as a single weekend. Despite upgrading infrastructure and optimizing resources, the migration time using Configuration Manager for Jira (CMJ) has proven to be too long, especially with extensive data sets.
...
Extended Migration Time: Snapshot creation and deployment times are taking significantly longer than expected.
High Resource Utilization: Despite using high-tier compute resources, migration processes consume considerable time, especially during the snapshot creation and deployment phases.
Re-indexing Delays: The re-indexing process, particularly after deployment, adds additional time to the overall migration.
Network and Storage Concerns: Possible network or storage latency issues could affect performance-based deployments.
Root Cause Analysis
The below ca
Data Volume and Complexity: The source and target instances contain millions of issues, hundreds of workflows, custom fields, and attachments. The sheer volume and complexity significantly increase the time required for snapshot creation, deployment, and re-indexing.
Single-threaded Operations: CMJ operations are single-threaded and do not leverage multi-threading or multiple database connections, limiting the ability to parallelize tasks and speed up the process.
Re-indexing Overhead: Re-indexing after data import is time-consuming and substantially delays the overall process.
Network Latency and Storage Performance: Possible network latency and suboptimal storage performance in the environment could contribute to longer migration times.
...