On Sun, 2021-02-21 at 12:56 +0300, İsmet BALAT wrote:
> And this state can be. Master machine can down and anorher machine
> can be new master. Then first machine can be online with master.Like
> in video. This state, I cant fix because no internet. This machines
> will use a offline project. All s
And this state can be. Master machine can down and anorher machine can be
new master. Then first machine can be online with master.Like in video.
This state, I cant fix because no internet. This machines will use a
offline project. All states have work successfully
On 21 Feb 2021 Sun at 12:45 İsm
I am testing aşk scenarios because I will use real machines with pacemaker.
Scenarios;
1-
node1 master
node2 slave
Shutting node1, then node2 become master
Successfully
2-
node1 slave
node2 master
Shutting node2, then node1 become master
Successfully
3-
node1 slave
node2 slave
One node become
My question is:
Why you are pausing one VM?there is any specific scope in that?you should
never have 2 master resources, pausing one vm could make unexpected
behaviours.
If you are testing failovers or simulated faults you must configure a
fencing mechanism.
Dont expect your cluster is working prop
Sorry, I am in +3utc and was sleeping. I will try first fix node, then
start cluster. Thank you
On 21 Feb 2021 Sun at 00:00 damiano giuliani
wrote:
> resources configured in a master/slave mode
> If you got 2 masters something is not working right. You should never have
> 2 node in master.
> Dis
resources configured in a master/slave mode
If you got 2 masters something is not working right. You should never have
2 node in master.
Disable pacemaker and corosync services to autostart on both nodes
systemctl disable corosync
Systemctl disable pacemaker
You can start the faulty node using pcs
I am not using fence. If I disable pacemaker,how node join cluster (for
first example in video - master/slave changing)? So I need a check script
for fault states :(
And thank you for reply
On 20 Feb 2021 Sat at 23:40 damiano giuliani
wrote:
> Hi,
>
> Have you correcly configure a working fenci
Hi,
Have you correcly configure a working fencing mechanism?without it you cant
rely on a safe and consistent environment.
My suggestion is to disable the autostart services (and so the autojoin
into the cluster) on both nodes.
if there is a fault you have to investigate before you rejoin the old
