-
Bug
-
Resolution: Fixed
-
Medium
-
8.13.0, 8.12.3, 8.20.0, 9.0.0, 9.1.0, 9.2.0, 8.13.26, 9.1.1, 8.20.13, 9.2.1
-
8.12
-
5
-
Severity 2 - Major
-
3
-
-
Issue Summary
This is reproducible on Data Center: yes
Since Jira 8.12 all entities (including issues) are versioned, i.e. each indexing operation on an entity has a unique version which is used to resolve conflicts and have a consistent state of data across all nodes and the DB.
Is it possible to have a DELETE issue indexing operation (with version X) followed by a reindex (UPDATE, UPDATE_WITH_RELATED) of an issue where an issue document may be created with the same version as the DELETE operation. This may cause in some situation the reindex (of a deleted issues) to win with the de-index operation.
Steps to Reproduce
- In a cluster with 4 nodes create an issue with 1000 subtask
- Just after creation delete the issue
Expected Results
The issue and all sub-tasks should be removed from the DB and all indexes (across all nodes).
Actual Results
Some sub-tasks may still be present on some indexes.
Workaround
Only full-reindex can fix indexes across the cluster.
- is blocked by
-
JRASERVER-73281 The status endpoint is taking longer to respond since Jira 8.20
- Closed
-
JRASERVER-74787 Full reindex operation slow down in Jira 9.0.0 caused by fetching issue versions from database in a single thread
- Closed
- is related to
-
JRASERVER-77499 Archiving an issue with subtasks can lead to index inconsistency
- Gathering Impact
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
BOOM-49 Loading...