Is there a way to get the migration assistants to use fewer resources and keep to the background?

[Rob Horan]

JCMA and CCMA can be a bit of a resource hog.  Is there any way to run these in more of a background mode so that users are not seriously impacted while a test migration is in progress?  This is a major issue when there are many GB of attachments.

[James Richards]

Hi,

Another solution is to set up a test instance locally that's a replication of your production server. You can get a developer licence for a local testing server to use. You can review this documentation on how to get one

• https://confluence.atlassian.com/jirakb/get-a-developer-license-for-jira-server-744526918.html

James.

[Derek White]

There is no publicly available documentation indicating it can be.

What we generally do is enable the attachment-only migration (which I believe is no longer a hidden feature flag) and do them off-hours, even for the test migration.

For prod, we generally migrate attachments the week prior to migration. When the prod migration goes over the weekend, this allows it to go much quicker as it only has to upload a diff of attachments and then re-link them to their issues.

IT may be able to setup some QoS rules based on the domain the Jira Server instance is communicating with. For example, you could lower the priority of the JCMA traffic. URLs and IPs can be found easily with a "atlassian JCMA ip whitelist" search.

Also, they recommend 6-8 GB of RAM for a small/medium instance and 10-12GB for a larger instance. This won't affect network resources, but you really didn't define "resource hog" so I don't have much to go off.