<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Kiall,<br>
<br>
Thank you for your reply. We hadn't recognized that Percona
cluster should be managed with odd-number nodes. We will consider
some options including Galera Arbitrator.<br>
<br>
Best regards,<br>
Nobumasa<br>
<br>
On 2015/03/14 0:02, Kiall Mac Innes wrote:<br>
</div>
<blockquote cite="mid:5502FBFA.4030303@macinnes.ie" type="cite">
<pre wrap="">Hi Yukutomi,
I believe the issue is that Percona Cluster requires an odd number of
cluster members. When you stop the B side Percona, the A side Percona is
unable to determine if the B side was stopped, of if there was a network
partition. Because of this, it stops accepting any SQL queries and
results in the behaviour you're seeing.
If you have 3x Percona's, or 2x Percona's and 1x Galera Arbitrator[1],
the DB cluster will remain functional during the loss of any single
cluster component.
Thanks,
Kiall
[1]: <a class="moz-txt-link-freetext" href="http://galeracluster.com/documentation-webpages/arbitrator.html">http://galeracluster.com/documentation-webpages/arbitrator.html</a>
On 13/03/15 11:24, Nobumasa Yukutomi wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi all,
I'm Nobumasa Yukutomi. I'm working on Designate since last year.
We are using Designate for '20141003' Git Hub repository of Icehouse.
We have built Designate with mysql(Percona) cluster shown below.
designate.conf designate.conf
IP:xxx.xx.x.x IP:yyy.yy.y.y
A-side B-side
----------------- -----------------
| designate-api | | designate-api |
----------------- -----------------
| |
----------------- cluster -----------------
| rabbitMQ |---------------| rabbitMQ |
----------------- -----------------
| |
-------------------- --------------------
| designate-central | | designate-central |
-------------------- --------------------
| |
|IP:xxx.xx.x.x |IP:yyy.yy.y.y
------------------ cluster ------------------
| mysql(Percona) |--------------| mysql(Percona) |
------------------ ------------------
| |
| |
----------------- -----------------
| PowerDNS | | PowerDNS |
----------------- -----------------
Let's assume some situation that mysql cluster encounters some problem. So
let's stop B-side mysql.
The A-side mysql(active) itself continues running. But designate-api
services of both sides stop working, even if the process of designate-api
continues running on both sides. User gets returned Error500(internal
server error) from designate-api.
Here are more details.
1. Listing domains
For example, if a user access designate-api of A-side, designate-central
accesses to both sides of mysql and the user experiences to succeed and
fail to list domains every other time.
2. Listing records
Also, listing records fails 100% in both sides when a user accesses to
designate-api of either A-side or B-side.
And here are my questions.
Question 1
In designate.conf of A-side, the destination of mysql is
A-side IP: xxx.xx.xx
In designate.conf of B-side, the destination to mysql is
B-side IP: yyy.yy.yy
But, for some reason, designate-central accesses to both IP addresses.
I would like to know why this is happening.
Question 2
I would like to know how to change configuration to make designate-central
to access "only" to active-mysql, not to inactive-mysql.
Thank you in advance.
Best regards,
---
Nobumasa Yukutomi <a class="moz-txt-link-abbreviated" href="mailto:yukutomi@m.ieice.org">yukutomi@m.ieice.org</a>
_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
---
Nobumasa Yukutomi <a class="moz-txt-link-abbreviated" href="mailto:yukutomi@m.ieice.org">yukutomi@m.ieice.org</a>
</pre>
</body>
</html>