Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monitor delay timeout changes are ignored #3

Open
arturq4 opened this issue Aug 2, 2019 · 0 comments
Open

Monitor delay timeout changes are ignored #3

arturq4 opened this issue Aug 2, 2019 · 0 comments

Comments

@arturq4
Copy link

arturq4 commented Aug 2, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant