-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
8.13.0, 8.20.0, 9.4.0, 8.13.27, 8.20.15
-
8.13
-
2
-
Severity 3 - Minor
-
1
-
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Create an issue with many sub-tasks
- Delete issue (with sub-tasks)
Expected Results
Operation should be relatively fast and not affect the cluster performance.
Actual Results
For every sub-task a re-index of the issue and sub-task is triggered.
Example: For an issue with 1000 sub-task deleting the issue triggers:
- 1000 re-index of main issue
- re-index of each sub-task (i.e. 1000)
- all this is followed by deleting this data from index
- the 2000 re-indexing operation are replicated across the cluster
Workaround
No workaround.
- relates to
-
JRASERVER-74424 Deletion of issues with Large number of issue links is very expensive leading to DB contention
-
- Gathering Impact
-
-
JRASERVER-70604 Cloning an archived issue fails
-
- Gathering Impact
-
-
JRASERVER-71577 Cannot delete a linked issue because of a locking session in the database
-
- Gathering Impact
-
-
JRASERVER-70162 Ability to auto-delete Archived issues
- Gathering Interest
-
JRASERVER-70614 Deleting an archived issue via REST API fails
- Gathering Interest
-
PSR-804 Loading...
Deleting an issue with many sub-tasks is slow and affects cluster performance
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
8.13.0, 8.20.0, 9.4.0, 8.13.27, 8.20.15
-
8.13
-
2
-
Severity 3 - Minor
-
1
-
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
- Create an issue with many sub-tasks
- Delete issue (with sub-tasks)
Expected Results
Operation should be relatively fast and not affect the cluster performance.
Actual Results
For every sub-task a re-index of the issue and sub-task is triggered.
Example: For an issue with 1000 sub-task deleting the issue triggers:
- 1000 re-index of main issue
- re-index of each sub-task (i.e. 1000)
- all this is followed by deleting this data from index
- the 2000 re-indexing operation are replicated across the cluster
Workaround
No workaround.
- relates to
-
JRASERVER-74424 Deletion of issues with Large number of issue links is very expensive leading to DB contention
-
- Gathering Impact
-
-
JRASERVER-70604 Cloning an archived issue fails
-
- Gathering Impact
-
-
JRASERVER-71577 Cannot delete a linked issue because of a locking session in the database
-
- Gathering Impact
-
-
JRASERVER-70162 Ability to auto-delete Archived issues
- Gathering Interest
-
JRASERVER-70614 Deleting an archived issue via REST API fails
- Gathering Interest
-
PSR-804 Loading...