Hi everyone! We’re glad to announce improvements to Jira indexation, that will help alleviate pressure on the indexing queues.
We’re introducing limits to the number of issue-related entities that can be reindexed at a time.
This feature will be enabled by default with the limit set to 1,000 of the newest entities (comments, change history records, and work logs). However, Jira admins can change the default value as well as turn the feature off. For more information and technical details, see our DAC announcement.
After enabling the feature, we guarantee that 1,000 newest comments, change history records, and work logs will be reindexed. We’re not deindexing entities that fall out of this pool. So, the actual number of indexed entities may be bigger than 1,000, but these extra entities won’t be reindexed in the future.
The improvements are included in Jira 8.22.2. Following 8.22.x release, the fix will be available in Jira 9.0.1 and 9.1.0.
Jira reindexing quality and index consistency got much better moving from Jira 6.x to Jira 8.x. Many things were fixed and we can safely assume that the quality of reindexing is good. As reindexing got more reliable, it still can be a very expensive operation. Triggered multiple times can cause the overload of the indexing queue and lead to significant performance problems (high CPU usage, timeouts for end-users), sometimes leading to instance failure.
You can find more details in the following ticket:
As part of the feature, we've added stats to help you gather information around the indexing of issue-related entities. You can find more details in this KB Jira indexing-limits stats | Jira | Atlassian Documentation
Andrzej KotasAtlassian Team
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event