You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have Pacemaker v.1.14 with manages SQL 2017 cluster in AWS.
SQL resource was added with command
`sudo pcs resource create SQLInstance ocf:mssql:fci op defaults timeout=60s --group sql-rg
I noticed SQL engine is started as a cluster resource at least 2 times because 20 sec timeout is exceed. I decided to change it to 60 sec with command
sudo pcs resource update SQLInstance op monitor interval=10s timeout=60s
It actually didn't change monitor behaviour. It still displays 20 sec timeout in a log and initiates SQL stop requests. It is a real problem as under load SQL stop-start 2-3-4 times in my case.
The text was updated successfully, but these errors were encountered:
I have Pacemaker v.1.14 with manages SQL 2017 cluster in AWS.
SQL resource was added with command
`sudo pcs resource create SQLInstance ocf:mssql:fci op defaults timeout=60s --group sql-rg
sudo pcs resource show SQLInstance
Resource: SQLInstance (class=ocf provider=mssql type=fci)
Operations: start interval=0s timeout=1000 (SQLInstance-start-interval-0s)
stop interval=0s timeout=20 (SQLInstance-stop-interval-0s)
monitor interval=10 timeout=30 (SQLInstance-monitor-interval-10)
defaults interval=0s timeout=60s (SQLInstance-defaults-interval-0s)
`
I noticed SQL engine is started as a cluster resource at least 2 times because 20 sec timeout is exceed. I decided to change it to 60 sec with command
sudo pcs resource update SQLInstance op monitor interval=10s timeout=60s
It actually didn't change monitor behaviour. It still displays 20 sec timeout in a log and initiates SQL stop requests. It is a real problem as under load SQL stop-start 2-3-4 times in my case.
The text was updated successfully, but these errors were encountered: