Can I run a JIRA background reindex at the same as a Zephyr reindex?

[Karalee]

We've had to run a background reindex of JIRA due to a index corruption. We also need to run a Zephyr reindex as our users cannot access Zephyr/execute tests until this is completed.

Will this corrupt the JIRA index?

Does the Zephyr reindex have any dependencies on the JIRA index?

[Sanjay Zalavadia · Accepted solution]

We do recommend that the JIRA re-index is run prior to the Zephyr for JIRA re-index.  Reason for this is because Zephyr refers to a bunch of JIRA data which, of course, is impacted by the JIRA re-index. 

Regards,

Sanjay

[Karalee]

Thanks Swapna. What we are asking is if they can be run at the same time - do Zephyr see any issues if the JIRA and Zephyr reindexes are run at the same time?

[Swapna Kumar Vemula _Zephyr_]

Hello Karalee,

It is recommended to perform JIRA or Zephyr re-indexing when major changes were done. And it is not mandatory to re-index both if the changes are specific, like if you have assigned many test cases to a cycle or executed bulk executions etc., then a Zephyr re-index will solve this issue. 

Once test issues have been created, modifying the configuration of your JIRA instance can result in search index out-of-sync with JIRA's configuration. In this case Zephyr re-index will make it work and JIRA index is required if the configuration changes are related to fields/schemes etc and mostly JIRA configuration related.

Since the dependency is not static, Zephyr has its own re-index function to sync the changes that made on testcases/execution/cycles. We suggest you to re-index Zephyr for JIRA if you find any issues related to test issues and JIRA index when there are plugin level changes like install/uninstall/upgrade etc.

Zephyr re-index will not corrupt any JIRA indexes instead it will build new indexes for latest changes if any.

For these reasons, it is recommended that you:

• Make all your necessary configuration changes in one go before starting the re-index process; and
• Start the re-index process in a time period of low activity for your instance.

Thank You,

Swapna Kumar Vemula