How To Disable Automatic Re-indexes After Upgrading

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products will end after February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


When upgrading JIRA, an automated re-index happens. For larger organizations that need to minimize downtime this can be a significant hassle, and a way to work around it is needed.


Due to JRASERVER-65568, this workaround will only work on Jira before 7.3.0 and Jira 8.0+.

For Jira 9, you may refer to this JRASERVER-74882 - Getting issue details... STATUS to add the additional JVM arguments.

  1. Edit or create <jira-home>/jira-config.propertiesEdit the file in Jira server.
  2. Add the line upgrade.reindex.allowed=false.
  3. To save further time, you may also want to add the line jira.autoexport=false to disable the automatic export that is generated as part of the upgrade process.
  4. Restart JIRA before your upgrade to ensure the properties are picked up. 

When using Jira on kubernetes these steps can be applied:

  1. Create a file named `jira-configmap.yaml` with the following content:
apiVersion: v1
kind: ConfigMap
  name: jira-configmap
data: |

2. Apply the ConfigMap to your Kubernetes cluster using the following command:

kubectl apply -f jira-config -map.yaml

3. Then, you need to mount this ConfigMap to your Jira pod. You can do this by modifying your Helm values. Create a file named `values.yaml` with the following content:

  - name: jira-config-properties
      name: jira-configmap

  - name: jira-config-properties
    mountPath: /var/atlassian/application-data/jira/

4. Upgrade Jira using the Helm upgrade command, include the `-f` flag to specify your `values.yaml` file:

helm upgrade --set image.tag=<your Jira version> -f values.yaml <your release name> atlassian/jira-software

5. This will upgrade Jira and set `upgrade.reindex.allowed=false` in ``.

After your upgrade, you may encounter a persistent "While upgrading Jira an upgrade task made changes that require reindexing" message while automatic reindexing on upgrades is disabled.

If you do, once your upgrade(s) are complete, remove the "upgrade.reindex.allowed=false" variable and restart Jira.

Last modified on Oct 27, 2023

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.