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

    • 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.

      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

            [JRASERVER-70422] Create Lucene document based replication for Jira DC for index replication

            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to JRASERVER-72045 [ JRASERVER-72045 ]
            Andriy Yakovlev [Atlassian] made changes -
            Description Original: h3. 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|https://confluence.atlassian.com/jirakb/lucene-index-synchronization-in-jira-data-center-800694054.html] for more details.

            h3. Suggested Solution
            Replicate Lucene document between nodes.
            Thus reduce overhead to recollect the CF values and recreate Lucene document.
             
            h3. Workaround
            None             		New: h3. 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|https://confluence.atlassian.com/jirakb/lucene-index-synchronization-in-jira-data-center-800694054.html] for more details.

            h3. Suggested Solution
            Replicate Lucene document between nodes (Document-based replication - DBR).
            Thus reduce overhead to recollect the CF values and recreate Lucene document.
             
            h3. Workaround
            None
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to JRASERVER-71857 [ JRASERVER-71857 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to JRASERVER-66265 [ JRASERVER-66265 ]
            Andriy Yakovlev [Atlassian] made changes -
            Link New: This issue relates to JRASERVER-68642 [ JRASERVER-68642 ]
            Maciej Swinarski (Inactive) made changes -
            Comment [ In Jira 8.12 we have added to Jira Document Based Replication: documents are only created on the source node (where the action triggering the change happened) and the document is then distributed to all other nodes. 

            Read more about DBR [here|https://confluence.atlassian.com/enterprise/document-based-replication-in-jira-data-center-1021214730.html]. ]
            Maciej Swinarski (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Maciej Swinarski (Inactive) added a comment -

            In Jira 8.12 we have added to Jira Document Based Replication: documents are only created on the source node (where the action triggering the change happened) and the document is then distributed to all other nodes. 

            Read more about DBR here.

            Maciej Swinarski (Inactive) added a comment - In Jira 8.12 we have added to Jira Document Based Replication: documents are only created on the source node (where the action triggering the change happened) and the document is then distributed to all other nodes.  Read more about DBR here .
            Maciej Swinarski (Inactive) made changes -
            Fix Version/s New: 8.12.0 [ 92098 ]
            Fix Version/s New: 8.13.0 [ 92100 ]
            Maciej Swinarski (Inactive) made changes -
            Assignee New: Maciej Swinarski [ mswinarski ]

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

                Created:
                Updated:
                Resolved: