-
Suggestion
-
Resolution: Fixed
Problem Definition
JIRA Datacenter will automatically keep all the copies of the index up to date automatically. This synchronisation is not fully synchronous, but aims for eventual consistency. This means that there is some delay before index changes are seen on other nodes in the cluster.
Each indexing operation writes a row to the database table replicatedindexoperation. All of the nodes then look for entries in this table that were inserted by nodes other than themselves. They then apply the changes to their local Lucene index by recollecting the CF values and recreating Lucene document.
see Lucene Index Synchronization in Jira Data Center for more details.
Suggested Solution
Replicate Lucene document between nodes (Document-based replication - DBR).
Thus reduce overhead to recollect the CF values and recreate Lucene document.
Workaround
None
- relates to
-
JRASERVER-72045 IndexException: Wait attempt timed out - waited 30000 milliseconds caused by background indexing tasks
- Closed
-
JRASERVER-66265 Null Pointer Exception thrown due to JIRA not handling correctly an inconsistency between the database and the lucene index.
- Closed
-
JRASERVER-68642 Deleted issues can be shown in searches in Jira DC
- Closed
-
JRASERVER-70423 DC index replication delays are affecting end-users due to single thread processing and re-computation of CF values
- Closed
-
JRASERVER-71857 Provide the versioning feature for replicated entities
- Closed
- mentioned in
-
Page Loading...