>>> FLORAC Thierry <thierry.flo...@onf.fr> schrieb am 09.03.2022 um 11:46 in Nachricht <pr2p264mb076751671fc57f33b995f851f5...@pr2p264mb0767.frap264.prod.outlook.com>:
> Hi, > > I manage an active/passive PostgreSQL cluster using DRBD, LVM, Pacemaker and > Corosync on a Debian GNU/Linux operating system. > Everything is OK, but my platform seems to be quite "sensitive" to small > network timeouts which are generating a cluster migration start from active > to passive node; generally, the process doesn't go through to the end: as > soon as the connection is back again, the migration is cancelled and the > database restarts! Could it be you run without fencing? Maybe show some logs! Logs are quite verbose and not very easy to understand... What log would you need? > That should be OK but on the application side, some database connections (on > a Java WildFly server) can become "invalid"! So I would like to avoid these > migrations when this kind of small timeout occurs... > > So my question is: which cluster settings can I change to increase the > timeout before starting a cluster migration? > > Best regards, > Thierry > > > > Thierry Florac > Resp. Pôle Architecture Applicative et Mobile > DSI ‑ Dépt. Études et Solutions Tranverses > 2, avenue de Saint‑Mandé ‑ 75570 Paris cedex 12 > Tél : 01 40 19 59 64 > www.onf.fr <https://www.onf.f<https://www.onf.fr>r
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
