Jira Data Center heap size and JVM tuning for a Cloud migration: setenv.sh and JCMA
Jira Data Center heap size and JVM tuning for a Cloud migration: setenv.sh and JCMA Key takeaways END STATE: a Jira Data Center 11.3 cluster on Java 21 whose heap is sized from your own GC log and Atlassian's migration table, whose setenv.sh carries only shipped or documented values, and whose nodes, pool, timeouts and background jobs are set for the Cloud Migration Assistant to run at full…
This guide outlines the process of sizing the heap and tuning the JVM for migrating a Jira Data Center 11.3 cluster to the cloud. The key steps include using Atlassian's migration table to determine the appropriate heap size based on factors like the number of issues, CPU cores, and node configuration. The setenv.sh file should only contain shipped or documented values, and the GC log should be analyzed to set the heap size and GC parameters.
The migration assistant should be configured with appropriate pool sizes, timeouts, and background job settings. The tutorial emphasizes sticking to Atlassian-provided guidelines and values wherever possible, while also allowing for optional adjustments based on specific circumstances. The goal is to ensure a smooth and efficient migration process while maintaining the stability of the Jira instance during the transition.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
