Best practices for when an instance is locked up during a migration with Project Configurator for Jira

During large project migrations using the Project Configurator for Jira, users may experience issues with instance locking or degraded performance. This article addresses potential causes and suggests solutions and best practices for managing these occurrences effectively.

Error message:

Open

Instance Locking

1. The “instance may lock during the actual data import”, as per Atlassian's "Restoring a Project From Backup" guidelines.

2. The instance locking behavior varies based on the project size and resource availability.

Best Practices

Resource Allocation

1. Ensure sufficient JVM heap space and allocate ample memory (recommendation: 32GB+ for projects with 100,000+ issues).

2. Use Jira's sizing guide to fine-tune your instance settings.

Migration Process

1. For large projects, avoid including attachment files in the migration to reduce data size. Instead, move attachments manually.

2. Schedule migrations outside office hours when possible to minimize user disruption and communicate planned downtime.

Ensure Stable Connectivity

• Check for stable internet connectivity during migrations to prevent timeouts or interruptions.