![]() $ cp mysql-connector-java-5.1.34-bin.jar /opt/atlassian/jira/lib/ $ tar -xzf mysql-connector-java-5.1.34.tar.gz Download the MySQL Java connector from MySQL’s download page, extract and copy the JAR file to JIRA library:.JIRA installation directory should be installed under /opt/atlassian/jira. ** Accept the default values except for ‘Default location for JIRA’, where you need to specify the NFS mount point, /mnt/jira as the default location for JIRA data. Download Atlassian JIRA installer and start the installer:.We will need to completely set up JIRA on the first node before proceeding to the second JIRA node. The following steps should be performed on jira1. Verify that you have mounted the NFS share correctly: $ df -hįilesystem Size Used Avail Use% Mounted on Mount the NFS share as listed inside /etc/fstab and change the permission of Jira mount point to 777:.Add the following line into /etc/fstab:ġ92.168.50.101:/export/jira /mnt/jira nfs rw,sync,hard,intr 0 0.Ensure you can see the NFS mount from the client host:.The following steps should be performed on jira1 and jira2. Restart NFS daemon to export the share directory:.Add the following line into /etc/exports:.Create a directory to be mounted as NFS shares:.$ apt-get install -y nfs-kernel-server nfs-common rpcbind The following steps should be performed on lb1. Alternatively, you can just kill the HAProxy process and let ClusterControl recover it. ** HAProxy installation from source does not come with init script, so kill and start the process as mentioned above to restart it. ![]() ![]() $ killall -9 haproxy & /usr/sbin/haproxy -D -f /etc/haproxy/haproxy.cfg -sf Restart HAProxy to apply the changes by killing the process:.Stick-table type ip size 1 nopurge peers LB On lb1 and lb2, open /etc/haproxy/haproxy.cfg and add the following lines: The failover scenario is further explained further down in the ‘Verifying the Architecture’ section. The other node will hold the active status, and if it goes down, then jira1 will become active again.To achieve this, we need to configure the HAProxy with stick-table. Since we are sharing the same JIRA home directory through NFS, we need to disable failback, which means if jira1 goes down and comes back up, it will remain passive. We need to add the load balancing definition for JIRA which will run on port 8080.You will now see the MySQL Galera Cluster with garbd installed as per below:Īt the moment, MySQL Galera Cluster is load balanced with virtual IP, 192.168.50.100 listening on port 3307. Go to Manage > Load Balancer > Install Garbd > choose the ClusterControl node IP address from the dropdown > Install Garbd. So, install garbd, a lightweight arbitrator daemon for Galera on the ClusterControl node from the ClusterControl UI. It is recommended to run Galera on at least three nodes.Enter the default admin email address and password on the welcome page and you should be redirected to the ClusterControl UI dashboard. The database cluster deployment will take about 15 minutes, and once completed, the ClusterControl UI is accessible at.$ cd ~/s9s-galera-codership-3.5.0/mysql/scripts/install/ Now we are ready to start the deployment:.Go to ~/s9s-galera-codership-3.5.0/mysql/config/ and remove the repeated node IP next to mysql_server_addresses so it becomes as below: Before we proceed with the deployment, we need to perform some customization when deploying a two-node Galera cluster.$ tar -xzf s9s-galera-codership-3.5.0.tar.gz Download and extract the deployment package:.In the wizard, we used the following values when configuring our database cluster (note that we specified one of the DB nodes twice under Database Servers’ text field) :ĭatabase Servers : 192.168.50.111 192.168.50.112 192.168.50.112Īt the end of the wizard, a deployment package will be generated and emailed to you. To set up Galera Cluster, go to the Galera Configurator to generate a deployment package.Ensure each host has proper FQDN set up as per host definition above.Ensure all hosts have the following host definition inside /etc/hosts:ġ92.168.50.102 lb2.local lb2 clustercontrol.jira2: JIRA (passive) + database server.lb2: HAproxy + keepalived (backup) + ClusterControl + garbd.JIRA and MySQL services are connected via a virtual IP to provide single point of access. Iptables is disabled to simplify the deployment. All hosts are running Debian Wheezy 64bit, we will use Galera Cluster for MySQL as database backend.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |