AWS 上での Jira Data Center のアップグレード

このページの内容

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

Before you begin, consider upgrading to an  Atlassian Enterprise release (if you're not on one already). Enterprise releases get fixes for critical bugs and security issues throughout its two-year support window. This gives you the option to keep a slower upgrade cadence without sacrificing security or stability. Enterprise releases are suitable for companies who can't keep up with the frequency at which we ship feature releases.

デプロイメントのアップグレードについて、次の点をご確認ください。

  1. Jira Data Center の最新バージョンにアップグレードする前に、アプリにそのバージョンとの互換性があるかを確認します。必要に応じてアプリを更新します。アプリの管理の詳細については、「Universal Plugin Manager の使用」を参照してください。
  2. アップグレード中もユーザーに Jira Data Center を提供する必要がある場合、ゼロ ダウンタイムで Jira Data Center をアップグレードすることをご検討ください。この方法ではノードを 1 つずつアップグレードしながら異なる Jira バージョンで動作させるため、アップグレード中もユーザーが Jira を利用できます。
  3. 本番サイトをアップグレードする前に、ステージング環境でアップグレードを実施することを強くおすすめします。「Jira のテスト環境を作成する」には、これを行うための便利なヒントが記載されています。

Choosing an upgrade method

If you deployed using our AWS Quick Start, you can upgrade your Jira version using either method:

Option 1: Normal upgrade

Performing a normal Jira Data Center upgrade on AWS involves three steps:

Step 1: Terminate all running Jira Data Center application nodes

Set the number of application nodes used by the Jira Data Center stack to 0. Then, update the stack. Doing this will make Jira Data Center unavailable (until you finish the next step). 

Click here for detailed instructions


  1. In the AWS console, go to Services > CloudFormation. Select your deployment’s stack to view its Stack Details.

  2. In the Stack Details screen, click Update Stack.

  3. From the Select Template screen, select Use current template and click Next.

  4. You’ll need to terminate all running nodes. To do that, set the following parameters to 0:

    1. Maximum number of cluster nodes

    2. Minimum number of cluster nodes

  5. Click Next. Click through the next pages, and then to apply the change using the Update button.

  6. Once the update is complete, check that all application nodes have been terminated.



Step 2: Update the version used by your Jira Data Center stack

Set the number of application nodes used by Jira Data Center to 1. Configure it to use the version you want. Then, update the stack again.

Click here for detailed instructions

  1. From your deployment’s Stack Details screen, click Update Stack again.

  2. From the Select Template screen, select Use current template and click Next.

  3. Set the Version parameter to the version you’re updating to.

  4. Configure your stack to use one node. To do that, set the following parameters to 1:

    1. Maximum number of cluster nodes

    2. Minimum number of cluster nodes

  5. Click Next. Click through the next pages, and then to apply the change using the Update button.

Step 3: Scale up the number of application nodes

You can now scale up your deployment to your original number of application nodes. For detailed instructions on how to do this, see Scaling up and down.

Option 2: Zero downtime upgrade

Performing a zero downtime upgrade of Jira Data Center on AWS involves four steps:

Step 1: Put Jira into upgrade mode

Jira をアップグレード モードにして、ノードを 1 つずつアップグレードする間にノードで異なるバージョンを実行できるようにします。

  1. In Jira, go to  > Applications > Jira upgrades.
  2. Click Put Jira into upgrade mode. This will only be available if your nodes are all on the same version.

Step 2: Find all the current application nodes in your stack

In AWS, note the Instance IDs of all running application nodes in your stack. These are all the application nodes running the older version of Jira. You'll need these IDs for a later step.

Click here for detailed instructions
  1. In the AWS console, go to Services > CloudFormation. Select your deployment’s stack to view its Stack Details.

  2. Expand the Resources drop-down. Look for the ClusterNodeGroup and click its Physical ID. This will take you to a page showing the Auto Scaling Group details of your Jira application nodes.
  3. In the Auto Scaling Group details, click on the Instances tab. Note all of the Instance IDs listed there; you'll be terminating them at a later step.

Step 3: Update the version used by your Jira Data Center stack

Increase the number of application nodes used by Jira Data Center by 1. Configure it to use the version you want. Then, update the stack.

Click here for detailed instructions
  1. From your deployment’s Stack Details screen, click Update Stack.

  2. From the Select Template screen, select Use current template and click Next.

  3. Set the Version parameter to the version you’re updating to.

  4. Increase the number of Jira application nodes used by your stack by 1. To do that, increase the following parameters:

    1. Maximum number of cluster nodes

    2. Minimum number of cluster nodes

  5. Click Next. Click through the next pages, and then to apply the change using the Update button.

Step 4: Terminate all nodes running the older version

In Step 2, you noted all nodes running the older version of Jira. You'll need to terminate them now.

Click here for detailed instructions
  1. In the AWS console, go to Services > EC2. From there, click Running Instances.

  2. Check all of the instances matching the Instance IDs you noted in Step 2.
  3. From the Actions drop-down, select Instance State > Terminate.
  4. Click through to terminate the instances.

Once you terminate all nodes running the older Jira version, AWS will automatically replace them. The new replacement nodes will automatically be running the new, upgraded Jira version.

Step 5: Finalize the upgrade

This step will allow any required upgrade tasks to run on your instance, and take Jira out of upgrade mode. Once the required tasks have completed, Jira will be fully upgraded.

  1. In Jira, go to  > Applications > Jira upgrades

  2. アップグレードを完了するをクリックします。これは、ノードがすべて同じバージョン (新しいバージョン) の場合のみ使用可能です。

これで、Jira インスタンスを新しいバージョンにアップグレードできました。 > [アプリケーション] > [バージョンとライセンス] から、現在のバージョンを確認することができます。

最終更新日 2019 年 7 月 28 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.