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

Remove the stale indexing Job associated with current node on startup

XMLWordPrintable

    • 1
    • 5
    • 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

      Currently, when Jira Datacente node is shutdown while running FullReindex task (see related JRASERVER-47045, JRASERVER-66204), there is no way to remove this task from the cluster. All other nodes still think the task is running even the node is down, so this prevents corresponding operations to be done. 

      Suggested Solution

      Add the start-up check which removes the stale indexing job. For a node which was shutdown ungracefully and then started again, it will clean up its own stale ForegroundReindex task.

      Implemented Solution

      • During the start-up, the node will find its own stale re-index task and remove it.
      • Jira is identifying reindex task by the node-id - to make sure it can be cleaned, please keep the same node-id.
      • If for some reason you cannot start the same node again (e.g. AWS instance got removed), we provide another way to remove the task from a cluster without a need to starting node again, see: JRASERVER-68616

      Workaround

      None

              dwlizlo Dawid
              ayakovlev@atlassian.com Andriy Yakovlev [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: