<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Percona on Pras' Labs</title><link>http://blog.pras.my.id/tags/percona/</link><description>Recent content in Percona on Pras' Labs</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 Dec 2016 10:00:54 +0700</lastBuildDate><atom:link href="http://blog.pras.my.id/tags/percona/index.xml" rel="self" type="application/rss+xml"/><item><title>Using ProxySQL to Access and Manage Percona XtraDB Cluster</title><link>http://blog.pras.my.id/blogs/2016-12-09-using-proxysql-to-access-and-manage-percona-xtradb-cluster/</link><pubDate>Fri, 09 Dec 2016 10:00:54 +0700</pubDate><guid>http://blog.pras.my.id/blogs/2016-12-09-using-proxysql-to-access-and-manage-percona-xtradb-cluster/</guid><description>&lt;p>We will use ProxySQL as a gateway to access our Percona XtraDB Cluster. ProxySQL is a high-performance SQL proxy. ProxySQL runs as a daemon watched by a monitoring process. The process monitors the daemon and restarts it in case of a crash to minimize downtime. The daemon accepts incoming traffic from MySQL clients and forwards it to backend MySQL servers.&lt;/p>
&lt;h2 id="installing-proxysql">Installing ProxySQL&lt;/h2>
&lt;h3 id="node-configuration">Node configuration&lt;/h3>
&lt;div class="pl-table-scroll" role="region" tabindex="0" aria-label="Table 1">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align: left">Node&lt;/th>
&lt;th style="text-align: left">Host&lt;/th>
&lt;th style="text-align: left">IP&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align: left">Node 1&lt;/td>
&lt;td style="text-align: left">db1&lt;/td>
&lt;td style="text-align: left">192.168.50.31&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: left">Node 2&lt;/td>
&lt;td style="text-align: left">db2&lt;/td>
&lt;td style="text-align: left">192.168.50.32&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: left">Node 3&lt;/td>
&lt;td style="text-align: left">db3&lt;/td>
&lt;td style="text-align: left">192.168.50.33&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: left">Node 4&lt;/td>
&lt;td style="text-align: left">proxysql&lt;/td>
&lt;td style="text-align: left">192.168.50.34&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h3 id="prerequisites">Prerequisites&lt;/h3>
&lt;ol>
&lt;li>
&lt;p>Install CentOS 7&lt;/p></description></item><item><title>Build Percona XtraDB Cluster using Ansible</title><link>http://blog.pras.my.id/blogs/2016-12-06-build-percona-xtradb-cluster-using-ansible/</link><pubDate>Tue, 06 Dec 2016 17:04:47 +0700</pubDate><guid>http://blog.pras.my.id/blogs/2016-12-06-build-percona-xtradb-cluster-using-ansible/</guid><description>&lt;p>Percona XtraDB Cluster is a database clustering solution for MySQL. It ensures
high availability, prevents downtime and data loss, and provides linear
scalability for a growing environment. Here we will try to install Percona
XtraDB Cluster on a three nodes cluster configuration with the help from
Ansible configuration management.&lt;/p>
&lt;h2 id="installing-percona-xtradb-cluster-on-red-hat-enterprise-linux-and-centos-7">Installing Percona XtraDB Cluster on Red Hat Enterprise Linux and CentOS 7&lt;/h2>
&lt;h3 id="node-configuration">Node configuration&lt;/h3>
&lt;div class="pl-table-scroll" role="region" tabindex="0" aria-label="Table 1">
&lt;table>
&lt;thead>
&lt;tr>
&lt;th style="text-align: left">Node&lt;/th>
&lt;th style="text-align: left">Host&lt;/th>
&lt;th style="text-align: left">IP&lt;/th>
&lt;/tr>
&lt;/thead>
&lt;tbody>
&lt;tr>
&lt;td style="text-align: left">Node 1&lt;/td>
&lt;td style="text-align: left">db1&lt;/td>
&lt;td style="text-align: left">192.168.50.31&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: left">Node 2&lt;/td>
&lt;td style="text-align: left">db2&lt;/td>
&lt;td style="text-align: left">192.168.50.32&lt;/td>
&lt;/tr>
&lt;tr>
&lt;td style="text-align: left">Node 3&lt;/td>
&lt;td style="text-align: left">db3&lt;/td>
&lt;td style="text-align: left">192.168.50.33&lt;/td>
&lt;/tr>
&lt;/tbody>
&lt;/table>
&lt;/div>
&lt;h3 id="prerequisites">Prerequisites&lt;/h3>
&lt;ol>
&lt;li>Install CentOS 7&lt;/li>
&lt;li>Update CentOS 7&lt;/li>
&lt;li>Open firewall for TCP ports 3306, 4444, 4567, 4568:&lt;/li>
&lt;/ol>
&lt;div class="highlight">&lt;pre tabindex="0" role="region" aria-label="bash code 1" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">ansible -i hosts -bkKv db-cluster -m firewalld -a &lt;span class="s1">&amp;#39;port=3306/tcp permanent=true
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="s1">state=enabled immediate=yes&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">ansible -i hosts -bkKv db-cluster -m firewalld -a &lt;span class="s1">&amp;#39;port=4444/tcp permanent=true
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="s1">state=enabled immediate=yes&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">ansible -i hosts -bkKv db-cluster -m firewalld -a &lt;span class="s1">&amp;#39;port=4567/tcp permanent=true
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="s1">state=enabled immediate=yes&amp;#39;&lt;/span>
&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">ansible -i hosts -bkKv db-cluster -m firewalld -a &lt;span class="s1">&amp;#39;port=4568/tcp permanent=true
&lt;/span>&lt;/span>&lt;/span>&lt;span class="line">&lt;span class="cl">&lt;span class="s1">state=enabled immediate=yes&amp;#39;&lt;/span>&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;ol>
&lt;li>
&lt;p>Disable or set SELinux to Permissive, set option below in &lt;strong>/etc/selinux/config&lt;/strong> and &lt;strong>/etc/sysconfig/selinux&lt;/strong>:&lt;/p></description></item></channel></rss>