JIRA Data Center のインストール

1. Upgrade your JIRA instance to 6.3 or later

See JIRA Installation and Upgrade Guide.

2. Connect your existing JIRA instance to your load balancer

Please perform your own load balancer testing based upon on what logic you use to route requests. Note that the easiest way to see which node a browser is connected to is in the footer.

3. Set up the JIRA file storage location on a separate server 

In this step, you need to set up a shared home directory that is writable by the JIRA instance and any future nodes, plus a "local home" directory for the exclusive use of this node.

You may already have your JIRA home directory on a networked file system, in which case you need to:

• ディレクトリは、他の潜在的なノードによる読み取りと書き込みができるようにします。
• Update your atlassian-jira/WEB-INF/classes/jira-application.properties file to point to a new local home directory that will not be used by the other nodes; this directory can either be truly local or located somewhere else on a networked file system
• Copy into this new location to the dbconfig.xml file

4. 既存の JIRA インスタンスをクラスター内で機能するように設定する

1. 既存の JIRA インスタンスに以下のものを設定します。

   • Put a cluster.properties file in the local JIRA home directory, with contents as follows:

     例を展開

     cluster.properties ファイルの例

      

     # This ID must be unique across the cluster jira.node.id = node1 # The location of the shared home directory forall JIRA nodes jira.shared.home = /net/mynfsserver/jira_shared_home

     詳細は、Cluster.properties ファイルのパラメーター を参照してください。

   • If using the Apache load balancer, set the Apache node name by appending the following setting to the same variable (replacing node1 with the node name used in the load balancer configuration):
     • -DjvmRoute=node1

2. Ensure the Base URL configured in JIRA is the URL of the front end proxy / load balancer.

3. If you use the Apache load balance, configure httpd: 

   Configuration example...

   If you use the Apache load balancer, configure httpd similarly to a standard reverse proxy, but with the addition of the mod_proxy_balancer configuration. Add a configuation block similar to this exampleat the end of http.conf:

   <VirtualHost *:80>         ProxyRequests off           ServerName MyCompanyServer           <Proxy balancer://jiracluster>                 # JIRA node 1                 BalancerMember http://jira1.internal.atlassian.com:8080 route=node1                 # JIRA node 2                 BalancerMember http://jira2.internal.atlassian.com:8080 route=node2                   # Security "we aren't blocking anyone but this the place to make those changes                 Order Deny,Allow                 Deny from none                 Allow from all                   # Load Balancer Settings                 # We are not really balancing anything in this setup, but need to configure this                 ProxySet lbmethod=byrequests                 ProxySet stickysession=JSESSIONID         </Proxy>           # Here's how to enable the load balancer's management UI if desired         <Location /balancer-manager>                 SetHandler balancer-manager                   # You SHOULD CHANGE THIS to only allow trusted ips to use the manager                 Order deny,allow                 Allow from all         </Location>           # Don't reverse-proxy requests to the management UI         ProxyPass /balancer-manager !         # Reverse proxy all other requests to the JIRA cluster         ProxyPass / balancer://jiracluster/         ProxyPreserveHost on </VirtualHost>

Verify that JIRA works correctly in the cluster by accessing JIRA through the load balancer and creating an issue with an attachment. Then check that this issue and attachment can be viewed/edited by another web browser through the load balancer.

5. 新しい JIRA ノードをクラスターに追加する

1. Install a new standalone JIRA instance by using one of the methods below. During the intallation, configure this new instance to use the same database and context path as the existing node(s). 
   1. Take a native backup of the original JIRA instance and copy it to the new node, then change the node ID from node1 to node2, or
   2. Perform a fresh install of JIRA 6.3 on the new node. Configure it by setting the home directory and editing/copying the dbconfig.xml and cluster.properties files as required before starting JIRA for the first time on the new node.
   3. In either case DO NOT import any data into the new node.
2. Configure it for clustering (as explained in Step 3). Ensure that its local home directory points to a different directory than the other nodes.

You can verify that data is correctly being synced to the new node by accessing the node directly and viewing the issue and attachment created earlier. 

6. この新しいノードをロードバランサに接続する

Atlassian assumes you or your IT department already knows how to do this. Please let us know if this is not the case.

Verify that the new node is in the cluster and receiving requests by checking the logs on each node to ensure both are receiving traffic and also check that updates done on one node are visible on the other. To find out which node a user is connected to simply check the cookie for the apache load balancer config.

各ノードで、手順 5 と 6 を繰り返します。