Versions Compared

Key

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

...

  1. 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.

  2. 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.

  3. Re-indexing Overhead: Re-indexing after data import is time-consuming and substantially delays the overall process.

  4. Network Latency and Storage Performance: Possible network latency and suboptimal storage performance in the AKS environment could contribute to longer migration times.

...

  • Exclude Attachments from Snapshots: Given the large size of attachments, exclude them from the snapshot. Instead, migrate attachments separately, following the best practices outlined in the Move Attachments.

  • Chunking the Migration: Instead of migrating the entire instance simultaneously, divide the data into smaller, manageable chunks. For example, split the projects into groups based on issue volume and migrate them sequentially. While not faster, this approach makes the process more manageable and allows partial completion within a weekend. Detailed guidance on chunking can be found in the How to deal with big snapshot deployments to optimize performance.

...

  • Skip Re-indexing During Deployment: To reduce time, skip re-indexing during deployment. Re-indexing can be performed manually after the data import is complete, as per the guidelines here.

  • Increase Compute Resources: Although already using high-tier resources, consider deploying a dedicated node in the AKS Jira Data Center cluster exclusively for CMJ operations. This setup can isolate CMJ processes and potentially reduce bottlenecks caused by shared resources.

...

  • Automate the Migration Process: Utilize CMJ's REST API to automate repetitive tasks such as issue key extraction, chunking, and snapshot creation. More information on automating these tasks can be found in REST API Automation.

Conclusion

...