Make Jira DC replication event retry mechanism more resilient

XMLWordPrintable

    • 0
    • 13

      Problem Definition

      As a workaround for JRASERVER-64922, a new mechanism has been added to Jira, that retries the failed index operation events.

      The current solution works in-memory (is not persistent), not attempting the retries if the node is restarted.

      Suggested Solution

      A potential improvement would be to store data about the operations to retry in the database.

      This would not only allow for a more resilient solution but also to potentially browse the historical data about the failed index replication requests across the DC cluster.

              Assignee:
              Unassigned
              Reporter:
              Andriy Yakovlev [Atlassian] (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: