Sometimes if you add a new resource or change something in your cluster configuration you get some warnings like this one.
Or if you run a configuration syntax check:
root@node1:~# crm configure verify
1 2 3 4 5 6 7
crm(live)configure# verify WARNING: mount_srv: default timeout 20s for start is smaller than the advised 60 WARNING: mount_srv: default timeout 20s for stop is smaller than the advised 60 WARNING: drbd_r0: default timeout 20s for start is smaller than the advised 240 WARNING: drbd_r0: default timeout 20s for stop is smaller than the advised 100 WARNING: pingnet: default timeout 20s for start is smaller than the advised 60 WARNING: pingnet: default timeout 20s for monitor_0 is smaller than the advised 60
Solution: define new operations, use the same times 240s and 100s
op start interval=”0″ timeout=”240s”
op stop interval=”0″ timeout=”100s”
1 2 3 4 5
primitive drbd_r0 ocf:linbit:drbd \ params drbd_resource="drbd0" \ op monitor interval="120s" \ op start interval="0" timeout="240s" \ op stop interval="0" timeout="100s"
Really dirty fix (set global timeouts):
crm configure property default-action-timeout="240"
Hello. I have a question. I wrote down the text.
First, I would like to know about the configurable scope of ha cluster (pacemaker, corosync, pcs).
Can you adjust the time when the primary is down and moving on to the secondary?
Can monitoring tools such as nagios and zabbix be implanted into the ha cluster?
Igor Drobot says
No problem, bee free to provide the information with a follow back link to my page :)
mlb jerseys size chart juniors says
Do you mind if I quote a few of your posts as long as I provide credit and sources back to your webpage? My blog is in the exact same area of interest as yours and my users would genuinely benefit from a lot of the information you provide here. Please let me know if this ok with you. Regards!