Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Priority: Highest
Fix Version/s: 9.12.0, 9.4.12
Affects Version/s: 9.0.0, 9.4.6, 9.4.7, 9.9.1, 9.4.8, 9.10.2
Component/s: Indexing
Labels:
- pse-request

Introduced in Version:
9
Support reference count:
22
Symptom Severity:
Severity 2 - Major
UIS:
221
Bug Fix Policy:
View Atlassian Server bug fix policy
Current Status:
Hide

Atlassian Update – 25 October 2023

Dear customers,

Thank you for taking the time to file and comment on this issue.
I'm happy to announce that we were able to deliver the improvement around foreground reindexing for Server instances to Jira 9.4.12. The fix is based on bringing two improvements in the way full reindex works from DC to Server licensed instances:

moving some steps of processing each issue from single-threaded to multi-threaded phase of the operation

changes in traversing db - loading more issues from database on each step, in order to dispatch whole batch instead of single issue per thread

The default size of these issues per thread batches is 50(in rare cases it's necessary, it can be changed by tuning the system property jira.custom.field.indexing.batch.size). Please note, that setting this property to 1 will disable using the improved path completely completely.

Michał Błajet
Jira DC Software Engineer
Show
Atlassian Update – 25 October 2023 Dear customers, Thank you for taking the time to file and comment on this issue. I'm happy to announce that we were able to deliver the improvement around foreground reindexing for Server instances to Jira 9.4.12. The fix is based on bringing two improvements in the way full reindex works from DC to Server licensed instances: moving some steps of processing each issue from single-threaded to multi-threaded phase of the operation changes in traversing db - loading more issues from database on each step, in order to dispatch whole batch instead of single issue per thread The default size of these issues per thread batches is 50(in rare cases it's necessary, it can be changed by tuning the system property jira.custom.field.indexing.batch.size ) . Please note, that setting this property to 1 will disable using the improved path completely completely. Michał Błajet Jira DC Software Engineer

Description

Issue Summary

The full reindex process has slowed down significantly for some customers. This is due to extra operations performed during reindexing that improve index correctness.

Steps to Reproduce

Update a Server-licensed instance to Jira 9.x.
Run full re-index.

Expected Results

There is no significant time degradation compared to 8.20.x.

Upgrading from 8.x to 9.x - Index changes

Full reindex process durations might slightly increase(our tests estimate this increase can be up to 3 minutes per 1M issues)

Actual Results

Operation takes significantly more time.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available.

Notes

DC-licensed instances where property jira.custom.field.indexing.batch.size is set to 1 in 9.x environment are also impacted by this Bug.
For DC-licensed instances who have NOT set jira.custom.field.indexing.batch.size=1, this issue is addressed in ~~JRASERVER-74787~~.

Attachments

Issue Links

relates to

JRASERVER-74787 Full reindex operation slow down in Jira 9.0.0 caused by fetching issue versions from database in a single thread

Closed

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(9 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Michelle Chin

Votes:: 32 Vote for this issue

Watchers:: 50 Start watching this issue

Dates

Created:: 28/Jul/2023 2:51 PM

Updated:: 08/Feb/2024 12:45 PM

Resolved:: 08/Nov/2023 2:09 PM