-
Suggestion
-
Resolution: Fixed
-
1
-
Atlassian Update - 6 June 2019
Dear Jira users,
we're glad to announce that this issue will be addressed in our upcoming 8.3.0 release!
The IndexAdmin page for Jira DC now checks the full re-index option by default and clearly marks this as the recommenced approach for DC reindexing. The changes applied are visible in the attached screenshot.
We plan to back port this fix to version 7.13 (our latest Enterprise Release version). Please watch the fix versions in this issue for further updates.
Looking forward to your comments.
Thank you,
Grazyna Kaszkur
Product Manager,
Jira Server and Data CenterAtlassian Update - 6 June 2019 Dear Jira users, we're glad to announce that this issue will be addressed in our upcoming 8.3.0 release! The IndexAdmin page for Jira DC now checks the full re-index option by default and clearly marks this as the recommenced approach for DC reindexing. The changes applied are visible in the attached screenshot. We plan to back port this fix to version 7.13 (our latest Enterprise Release version). Please watch the fix versions in this issue for further updates. Looking forward to your comments. Thank you, Grazyna Kaszkur Product Manager, Jira Server and Data Center -
Problem
Currently JIRA offers an in product UI that advises JIRA administrators to run an index after major changes are performed. It would be nice if the reindex page itself had some details on running a background vs. foreground index which could discourage the use of a background index specifically when in datacenter mode.
Note
from docs Search indexing
On a multi-node Jira Data Center, you can use the Lock Jira and rebuild index option without actually locking the instance. Therefore, if your Data Center instance has multiple nodes, don't bother with a Background re-index.
- duplicates
-
- Closed
- is resolved by
-
JRASERVER-47045 When a re-indexing node is abruptly stopped indexing still shows as in progress on other nodes, preventing future reindexing
-
- Closed
-