Hi Mark,
nothing happens to the VIP? As it is, the agent is not monitoring
mysqld itself. In my case, I call mysqld_safe so the kill -9 would be
handled. I am out for a few days, answers will be delayed until end of
next week.
Regards,
Yves
On 12-02-09 06:04 PM, Mark Grennan wrote:
Y
Yves
I've been testing the Master-Master / Pacemaker / MHA failover with some good
results.
Oddly, the one thing that is not happening is, if I just kill -9 mysql
Pacemaker doesn't see it.
Pulling the network cable works good. This is a really the worst thing to do.
Pacemaker sees it and tu
Hi,
even if you fix the schema, sending simultaneous write to the 2
masters will cause issues with replication. You also have no
performance gain from such a setup since both masters will have to
perform all the writes anyway Best is to write only to one at a time.
The new mysql RA (not
On Sat, Jan 28, 2012 at 5:45 AM, Peter Scott wrote:
> On 1/26/2012 8:12 PM, gustavo panizzo wrote:
>>>
>>> crm_mon says it is starting mysqld on mysql01.
>>> (I think it actually stopped and restarted mysqld on mysql01 but
>>> haven't been able to verify yet. Seems gratuitous, but I can live
>>>
On 1/26/2012 8:12 PM, gustavo panizzo wrote:
crm_mon says it is starting mysqld on mysql01.
(I think it actually stopped and restarted mysqld on mysql01 but
haven't been able to verify yet. Seems gratuitous, but I can live
with that though.)
do not start clustered services from init
this is n
On Thu, Jan 26, 2012 at 06:56:28PM -0800, Peter Scott wrote:
> mysql02 starts mysqld from init.
do not start clustered services from init
> mysql01 starts mysqld from init.
> crm_mon says it is starting mysqld on mysql01.
> (I think it actually stopped and restarted mysqld on mysql01 but
> haven't
On 1/25/2012 11:29 PM, Florian Haas wrote:
Well if you just want to restart Corosync by administrative
intervention (i.e. in a planned, controlled fashion), then why not put
the cluster in maintenance mode before you restart Corosync? Cheers,
Florian
Good point. My concern was about whether th
On 1/26/12 5:25 AM, Dan Frincu wrote:
Hi,
On Thu, Jan 26, 2012 at 1:43 AM, Peter Scott wrote:
> Hello. Our problem is that a Corosync restart on the idle machine in a
> 2-node cluster shuts down the mysqld process there and we need it to stay
> up for replication. We are very new to Coros
Peter Scott wrote:
Here's the detail: We have two MySQL comasters (each is a master and a
slave of the other). Traffic needs to arrive at only one machine at a
time because otherwise conflicting simultaneous updates at each machine
would cause a problem.
If this is true then your database de
Hi,
On Thu, Jan 26, 2012 at 1:43 AM, Peter Scott wrote:
> Hello. Our problem is that a Corosync restart on the idle machine in a
> 2-node cluster shutds down the mysqld process there and we need it to stay
> up for replication. We are very new to Corosync and Pacemaker and have been
> slogging
On Thu, Jan 26, 2012 at 12:43 AM, Peter Scott wrote:
> Hello. Our problem is that a Corosync restart on the idle machine in a
> 2-node cluster shutds down the mysqld process there and we need it to stay
> up for replication.
Well if you just want to restart Corosync by administrative
interventio
Hello. Our problem is that a Corosync restart on the idle machine in a
2-node cluster shutds down the mysqld process there and we need it to
stay up for replication. We are very new to Corosync and Pacemaker and
have been slogging through every tutorial and document we can find.
Here's the d
12 matches
Mail list logo
