[ClusterLabs] Antw: Replicated PGSQL woes

[Keisuke MORI]

2016-10-14 16:36 GMT+09:00 Ulrich Windl <Ulrich.Windl at rz.uni-regensburg.de>:
>>>> Israel Brewster <israel at ravnalaska.net> schrieb am 13.10.2016 um 19:04 in
> Nachricht <34091524-D35E-4E28-9C3E-DDA6C6A1E362 at ravnalaska.net>:
> [...]
>> Oct 13 08:29:39 CentTest1 crmd[30096]:   notice: State transition S_IDLE ->
>> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL
>> origin=abort_transition_graph ]
>> Oct 13 08:29:39 CentTest1 pengine[30095]:   notice: On loss of CCM Quorum:
>> Ignore
>> Oct 13 08:29:39 CentTest1 pengine[30095]:   notice: Stop
>> virtual_ip#011(centtest2.ravnalaska.net)
>> Oct 13 08:29:39 CentTest1 pengine[30095]:   notice: Demote
>> pgsql_96:0#011(Master -> Stopped centtest2.ravnalaska.net)
>> Oct 13 08:29:39 CentTest1 pengine[30095]:   notice: Calculated Transition
>> 193: /var/lib/pacemaker/pengine/pe-input-500.bz2
>
>> Oct 13 08:29:39 CentTest1 crmd[30096]:   notice: Initiating action 43:
>> notify pgsql_96_pre_notify_demote_0 on centtest2.ravnalaska.net
>> Oct 13 08:29:39 CentTest1 crmd[30096]:   notice: Initiating action 45:
>> notify pgsql_96_pre_notify_demote_0 on centtest1.ravnalaska.net (local)
>
> The above section looks wrong, because if one resource is master and the other is slave, both cannot be demoted (AFAIK).. I'm also surprised that the cluster tries to demote a failed master; maybe you have no fencing configured?


Those are "notification" operations before the demote and it is
correct being sent to all the nodes in the cluster.


>
>> Oct 13 08:29:39 CentTest1 crmd[30096]:   notice: Operation
>> pgsql_96_notify_0: ok (node=centtest1.ravnalaska.net, call=230, rc=0,
>> cib-update=0, confirmed=true)
>> Oct 13 08:29:39 CentTest1 crmd[30096]:   notice: Initiating action 6: demote
>> pgsql_96_demote_0 on centtest2.ravnalaska.net
>
> "action 6": Where does it come from? We had 43 and 45!

This is the actual "demote" operation.


-- 
Keisuke MORI