We have done successful server to cloud migration for one of our project board. Now we are trying another board but we are getting error.We had a look at the error reports for migration and we couldn't see anything obvious about why the migration for failed. we do have an warning though when creating the migration about the heap size being below recommended. But it's warning, so do we need to fix all warnings or otherwise migration would fail?
Hi @Savita Fulmali and welcome to the Community!
These warnings are obviously there for a reason. You do not need to fix everything you see, but these warnings are there because it is known that certain things may make your migration fail. It is always better to prevent these things from happening rather than having to roll back or fix errors afterwards.
Hope this helps!
Hi,
So, are you suggesting to increase heap memory size on Jira server to fix the warning.
I am bit hesitant to do so as we have never got any issue with memory.
I have attached current memory utilization.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, not able to attach image.
Below are our Jira server JVM configuration.
JVM_MINIMUM_MEMORY="1024m"
JVM_MAXIMUM_MEMORY="2048m"
Also, we have around 500 Jira users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Savita Fulmali,
There is a checklist pre-migration where you can verify recommended settings and a lot of other things to verify in this support article.
Cloud migration is not regular use of your Jira instance, so I can only recommend to follow the suggestions that are being made there.
That still does not guarantee that you won't run into any issues while migrating, though. Cloud migration is a complex matter, but it's always going to be better to follow recommendations to avoid (potential) known issues.
If - despite your precautions - something goes wrong, it is best to look at the log files and if necessary reach out to Atlassian Migration Support and create a ticket with detailed error information there.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.