I am setting up a pacemaker resource for Percona 5.7 on CentOS 7 latest.
According to the release notes for 5.7 systemd handles what safe_mysqld did.
I'm wondering if I can update the resource appropriately. Do I need to
revert to 5.6 until this is supported?
* mysql_start_0 on localhost 'not
On 04/15/2016 12:29 PM, Digimer wrote:
> That is what I assumed. Sorry, at a trade show so I'm reading and
> replying quickly.
I didn't spell it out, but that would be too easy.
However, it's not happening today. My guess is it was somehow caused by
DRBD being in inconsistent state: I didn't
On 04/15/2016 04:59 PM, Dmitri Maziuk wrote:
> On 2016-04-15 07:46, Klaus Wenninger wrote:
>
>> Which IP-address did you use to ssh to that box? One controlled
>> by pacemaker and possibly being migrated or a fixed one assigned
>> to that box?
>
> Good try but no: the "sunken" (as opposed to
On 2016-04-15 07:46, Klaus Wenninger wrote:
Which IP-address did you use to ssh to that box? One controlled
by pacemaker and possibly being migrated or a fixed one assigned
to that box?
Good try but no: the "sunken" (as opposed to floating ;) address of course.
If what digimer says is true,
On 04/15/2016 02:22 PM, Digimer wrote:
> On 14/04/16 05:38 PM, Dimitri Maziuk wrote:
>> Hi all,
>>
>> I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
>> cluster running drbd (8.4) and apache. It's all working fine except when
>> I trigger a fail-over, my ssh connection to
On 04/15/2016 02:21 PM, Digimer wrote:
> On 15/04/16 03:12 AM, Andrey Rogovsky wrote:
>> Hi
>> How to suicide works?
>> I want to reboot node when it lost networking and get out from cluster.
> Stonith can't really on the failed/lost node behaving in any predictable
> way. So self-fencing, ssh
On 14/04/16 05:38 PM, Dimitri Maziuk wrote:
> Hi all,
>
> I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
> cluster running drbd (8.4) and apache. It's all working fine except when
> I trigger a fail-over, my ssh connection to active (being demoted) node
> gets cut.
>
>
Hi all,
I've an up to date centos 7 w/ pcs + corosync + pacemaker active-passive
cluster running drbd (8.4) and apache. It's all working fine except when
I trigger a fail-over, my ssh connection to active (being demoted) node
gets cut.
Am I missing something or is this an expected behaviour of
Hi
How to suicide works?
I want to reboot node when it lost networking and get out from cluster.
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: