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
don't remove LOCK file when PGSQL stopped with quorum lost. #28
Comments
One answer found http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html-single/Pacemaker_Explained/#_multi_state_notifications But the meaning is not quite clear. Or should we switched on and off in the correct order. |
It may be a bug of pacemaker. |
You mean to say, that after the loss of a quorum pacemaker should send a message to stop all the resources and reset this variable($OCF_RESKEY_CRM_meta_notify_slave_uname), because resource master-slave too must be stopped? |
Yes. |
In the comparison above:
Why the space between the " " for the comparison target? Seems like an error to me. The OCF_RESKEY_CRM_meta_notify_slave_uname got trim'ed upon import, so blank strings would have become empty strings, no? |
Hi, |
I dont know. My project was closed. I almost was not interested in the topic. |
I have the same problem with 2 nodes cluster. The LOCK is never deleted as OCF_RESKEY_CRM_meta_notify_slave_uname always contains so the slave can't be restarted. Perhaps this file can be deleted on slave successful stop after wal sync check |
Hi furynick Sorry, I switched to another task 5 years ago. This agent was merged into ClusterLabs repository and maintained at its community. |
Thanks for reply, I already found related issue at ClusterLabs#699 |
Hi!
I again found trouble. )
I doing experiment with quorum lost.
After quorum lost LOCK not deleted.
I see code.
Where defined $OCF_RESKEY_CRM_meta_notify_slave_uname ? what he mean?
The text was updated successfully, but these errors were encountered: