Project Configurator relies on Jira's data transfer technology when importing project data. As stated in the documentation, import of complete projects (i.e their configuration, issue data, and attachments) is subject to the restrictions described in Atlassian’s Restoring a Project From Backup. In the mentioned article, Atlassian state the following:

The instance lock during project imports typically occurs during specific phases of the import cycle, particularly when data is being migrated and synchronized. This locking is often temporary and may not be noticeable depending on the size and complexity of the import, as well as the resources available to the system.

During the import process, the system may lock certain resources or functionalities to prevent conflicts or data inconsistencies. This lock ensures the integrity of the imported data and maintains system stability.

However, the duration and extent of the lock can vary based on factors such as the volume of data being imported, the performance of the server infrastructure, and any concurrent activities on the instance.

If you haven't observed a noticeable instance lock during your project imports, it's possible that your system setup or configuration is handling the process efficiently without causing significant disruption to users. However, it's still essential to be aware of potential impacts and to plan imports accordingly, especially for larger or more complex migrations.

With a 4-node Data Center (DC) instance, you have the advantage of distributed resources, which can help mitigate the impact of in-progress imports on instance performance and user experience. Here are some insights and recommendations tailored to your setup:

1. Resource Isolation: Since one of the nodes is designated for admin use only, consider leveraging this node to perform the imports. By isolating the import process to a dedicated node, you can minimize the impact on regular user activities across the other nodes.

2. Load Balancing: Ensure that your load balancer is configured to distribute user traffic evenly across the available nodes. This helps prevent overloading any single node during the import process and maintains optimal performance for users accessing the instance.

3. Node Capacity: Evaluate the resource capacity of each node in your DC instance and distribute the import workload accordingly. Assign the import tasks to nodes with sufficient resources to handle the load without impacting the performance of other nodes.

4. Monitoring and Scaling: Monitor the resource utilization and performance metrics of each node during the import process. If necessary, consider scaling up resources (e.g., adding more nodes) temporarily to accommodate the increased workload and maintain optimal performance.

5. Incremental Imports: Break down the import tasks into smaller, incremental batches to distribute the workload more evenly across the nodes. This approach can help prevent resource contention and minimize the impact on instance performance.

6. Database Optimization: Optimize database performance by ensuring that database indexes are properly configured, database caching mechanisms are utilized effectively, and database queries are optimized for efficiency. This can help improve the overall responsiveness of the instance during imports.

7. Communication: Keep users informed about the scheduled import and potential impact on their workflows. Provide updates on the progress of the import process and any temporary disruptions they may experience.

By implementing these recommendations and leveraging the capabilities of your 4-node DC instance, you can minimize the impact of in-progress imports on instance performance and user experience, ensuring a smoother transition of projects/issues into your production environment.

Answer to Question 3.

Answer to Question 4.

Answer to Question 5.