Problem Definition

Jira DC replication might lose some events or make Lucene not up to date with DB, see related JRASERVER-68528, JRASERVER-68400

Suggested Solution

• Provide the versioning feature for replicated entities in DC
• Change the way how replicated operations are replayed

In the fixed version:

• we have added versioning of all entities - now every change which triggers an issue, comment or worklog reindex bumps this entity version (bumping the version is only triggered by user actions, not full/background re-index)
• on both server and DC there is a task running every 5sec which checks the consistency of the recent (last 15 sec) changes in the index and re-applies deletes if there was a late update which has overridden the delete (conditional updates do not solve this problem); this task checks for the consistency of updates as well to handle corner cases like thread was gone after updating the DB (for DC this is the index replication table, for server the entity version table) but before updating the local index

Workaround

None