Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70422

Create Lucene document based replication for Jira DC for index replication

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      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

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-72045 IndexException: Wait attempt timed out - waited 30000 milliseconds caused by background indexing tasks

          • Highest - Our top priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-66265 Null Pointer Exception thrown due to JIRA not handling correctly an inconsistency between the database and the lucene index.

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-68642 Deleted issues can be shown in searches in Jira DC

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-70423 DC index replication delays are affecting end-users due to single thread processing and re-computation of CF values

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-71857 Provide the versioning feature for replicated entities

          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              mswinarski Maciej Swinarski (Inactive)
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: