Application of MySQL Cluster to Build Two-
Way Distribution of Distributed Database
with Application of Fail Over and Load
Balancing Method
Pascal Jezequel Mario Campone Wilfried Gouraud
Catherine Guerin-Charbonnel Christophe Leux
Gabriel Ricolleau Loc Campion
Abstract - An organization or
company must have in it an
adequate information system.
Information systems are usually
used to facilitate employees /
clients / stakeholders who play a
role in it to seek information.
With the existence of complex
information systems required a
database storage to support the
running of the information
system. In reality, often
encountered a condition where
the information system when
accessed by the client
sometimes failure. Failure is like
a failure on the required system
against the database. So the
failure of the database, the
automatic is very closely related
to the server so it appears like
the failure. Usually it happens
because the server is off or down
or the network is disconnected
so that the client can not access
the existing data on the
database server. Therefore the
solution of the problem that is
required at least two servers
(Master-Slave) for database
storage is High Availability. So
that the client in accessing the
server database if the failure
encountered will be directly
replaced or served by another
server with the same database.
To accomplish this, we use the
Fail Over methodology with
Replicate Two-Way Database and
Load Balancing with the
assumption that the workload of
each server can be shared. With
the application of this method
obtained the results of the
server one and the other can
backup each other data, and also
when the server one down it can
be replaced by other servers. So
it can be concluded that the
implementation of Database
Replication with Failover and
Load Balancing can provide
solutions especially for
companies or organizations that
are in need of availability of
server data, in this case that is
High Availability.
Keywords-Replication,
MySQL Cluster, Fail Over, Load
Balancing.
I. INTRODUCTION
Problems here the author took
from the results of previous journal
reviews, such as the journal entitled
"Population Data Distribution In
Gorontalo City Using Database
Replication Methods With Single
Master Replicated Techniques"
Where from the above journals
there is a problem that is the
availability of data is still centralized,
then completed by the author of the
journal with the method that the
authors sense is still lacking. So this
writer thinks there is a need for a
development technique that can
solve the problem with several
methods that are closely related to
the distributed data base.
Based on the issues discussed
in this journal, can be drawn some
discussion of issues that refers in the
theme or title (Building Replication
Two-Way Distributed Database with
Application of Fail Over and Load
Balancing Method) as follows,
namely: Understanding the concept
of two-way Replication in database
design Distributed, two-way
replication configuration with
combination of Failover and Load
Balancing methods, the advantages
of two-way Database Replication with
Failover and Load Balancing
methods, Implemantation of Two-way
Replication with Failover and Load
Balancing methods.
II. METHODOLOGY
2.1. Two-way Replication
Database replication aims to
duplicate a server, so that the
database has duplicates on other
servers.
Two-way replication means not
only one server can duplicate data to
another server, but one server and
the other can duplicate each other's
data and in this context the roles of
both servers are the same.
2.2. MySQL Cluster
The three main nodes that are
components of MySQL cluster
include:
A pair of Data Nodes that are
used to store all transaction data on
the MySQL cluster and the data is
replicated on this node, the
Management Server Node is used to
control the processes on the system
when it is turned on. In addition, this
node is also used to identify any
configuration changes, MySQL Server
API Node is an interface used by the
client to access data and manipulate
data on the cluster system.
2.3. Failover
Failover is the process of
automatically switching a server
when another server is experiencing
a problem or malfunction or can also
be said to be duplication and data
backup.
This process can occur without
stopping the running process so that
the movement is done by the cluster
system itself. This type of clustering
is more intended for data duplication
so that the client can still access the
data information service even though
the server side is actually being
interrupted.
2.4. Load Balancing
Load balancing is a technology
of sharing internet traffic or work
processes on multiple servers using
hardware and software in a computer
network and can be run as a router.
This clustering system serves to
distribute the traffic load on two or
more connection lines in a balanced
way so that traffic can run optimally
with a small response time and
optimal process.
Load balancer will receive a
traffic from the client and then the
traffic is continued to some other
server. The traffic will be sorted by
client request and server condition.
When only one client requests, the
process happens only on one server.
Whereas when exceeded, the load
balancer will divide the process in a
balanced manner for each server.
2.5. Network Architecture
Here will be described the
architecture or network scheme
MySQL Cluster and Load Balancing:
Figure 1. MySQL Cluster Topology and
Load Balancing
In Figure 1 it can be
interpreted that Managent Node
Sever acts as a controller or
controller than other server nodes.
2.6. Physical Data Model (PDM)
This is a database scheme
which will be replicated later.
In Figure 2 is a Physical Data
Model scheme, here the authors use
a subdistrict database consisting of
several tables including: Accounts,
Profiles, Employees, Positions,
Salaries, Allowances, and others.
III. RESULTS AND DISCUSSION
Here the writer first discuss the
connection problem between node-
node sever to be able to duplicate
data between server one and other
server, as below:
3.1. Connection between Node Sever
and Management Server
Figure 3. View Connection between
server nodes in Management Node
If it looks like picture 3 then it is
certain to do two way replication.
Next do initialization on the server
node to be recognized on the
management node, as below:
Figure 4. Initialization process on
Node Server
In Figure 4. It has been seen that
both server nodes have been
initialized in order to be recognized
by Management Server.
3.2. Two-way Replication
The authors apply a two-way
relication where the two servers can
duplicate data, either server one or
the other server.
Figure 5. Replication Results
The data inputted by Node One
automatically replicates on the
Second Server Node. Terms to be
able to replicate here is the second
database server must be NdbCluster
engine because this replication using
MYSQL Cluster so if you use the
default built-in MySQL engine
MyIsam then the replication process
will not be able to run. Figure 5. As
proof that the query results
successfully entered.
3.3. Failover and Load Balancing
Here are the results of failover
testing:
Figure 6. The second condition of the
Node Server is on
Node one on Load Balancing shows
that DownTime looks 12m53s when
it is on live condition.
Figure 7. Conditions when Node one
is turned of
When Server Node One is turned of
then there is a change on DownTime
to 17s. At the condition of Node one
is dead then the data query result
data when executed by the user will
temporarily be moved to the server
that is still running, in the picture
above then, the query data will be
moved to the Node two server to be
stored and the replication process
will run if the Node server one live
back.
Figure 8. Conditions when no
incoming queries
For this we can look at Session Max,
where the value is 0, because there
is no query yet.
Figure 9. Conditions after the data
query occurred
When the data query occurs, it can
be seen in Session Max will change
the value to 1 where this value 1
indicates the occurrence of the data
query process.
IV. CONCLUSION
Based on the results of
research, it can be concluded that to
run the replication of both server
nodes one and two must have been
running first and can be connected
with Management Node. After the
Management Node Getting the
position of the two Nodes, then it can
be run two-way replication.
From the test results from the
server Node One obtained value at
the time of the data query process
then the query results are captured
by the second Node database and
vice versa. So Load Balancing here is
very helpful server performance
because it can play a role to share
the burden between the two servers.
Suggestion of development proposed
by the writer that is for the next can
be done application of Failover
method with HeartBeat.
BIBLIOGRAPHY
[1] Eddy Purwanto. 2012.
"Comparison of Replication Strategy
in Distributed Database System".
Journal of Bina Darma University
Palembang, Vol. 5, No. 10, 2012.
[2] Abdul Gani, Taufiq. "MySQL
Cluster Performance Analysis Using
Load Balancing Method". Journal of
Electrical Engineering, Vol.11, No. 4,
August 2015.
[3] Raentantyo Wardoyo. 2012.
"Code Diferences in Rancanagn
Database and Settlement Strategy
for Synchronizing Data". Journal of
IPTE-KOM, UGM, Vol. 14, No. 2, 2012.
[4] Deshanta Ibnugraha, Prajna.
"Design and Development of Failover
System In MySQL Using Heartbeat
and MySQL Native Replication to
Support Online Data Availability".
Journal of Information Technology of
Telkom Polytechnic, Vol. 1, No. 3, May
2012.
[5] Silitonga, Parasian. "Database
Replication In The Academic Data
Processing System of St. Thomas
Catholic University". Journal of TIME,
Vol. 3, No. 1, 2014.