Hi,
May I get an answer please?
Kind regards,
––
Qusay Jibrail
Senior Infrastructure Engineer – Linux | GfK IT Services
GfK – an NIQ company | The Netherlands
Krijgsman 22-25 | Amstelveen | 1186 DM
T: +31 88 435 1232 | M: +31 628 927 686
Approach with alert agent is working now. It requires to call "pcs resource
cleanup" by root using sudo, add "sleep 120" before calling pcs utility in
alert agent script and increase alert agent timeout adequately.
But I don't like this workaround, it takes too long a time to switch
primary node
On Fri, Oct 6, 2023 at 8:46 AM Sergey Cherukhin
wrote:
> Hello!
>
> I used Microsoft Outlook to send this message and it was sent in the wrong
> format. I'm sorry. I won't do it again.
>
> I use Postgresql+Pacemaker+Corosync cluster with 2 Postgresql instances in
> synchronous replication mode.
Hello!
I used Microsoft Outlook to send this message and it was sent in the wrong
format. I'm sorry. I won't do it again.
I use Postgresql+Pacemaker+Corosync cluster with 2 Postgresql instances in
synchronous replication mode. Parameter “rep_mode” is set to "sync", and
when I shut down the
