Details
-
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 -
Description
Summary
In large data center environment (for example, Jira has over 1 million issues), background reindex was generating load and putting pressure on GC by generating objects and then releasing them after. On top of that, user activities add more load to the system. User might experience performance issue CPU spike and some significant impact.
Documentation
We have mentioned the background reindex impact in Jira Indexing FAQ
Background reindexing uses just a single thread and in theory should trundle along in the background without significant impact on the rest of JIRA. In some circumstances though it may have a significant impact. On large systems under heavy load with a high rate of issue searches then there may be some significant impact, and it may be wise to perform the re-index during a period of lower activity, e.g. in the middle of the night
Suggestion
It would be nice to add some notification or warning message in the index page in JIra's UI indicate the impact for large data center environment.
Attachments
Issue Links
- is duplicated by
-
- 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
-
- mentioned in
-
Page Loading...