-
Notifications
You must be signed in to change notification settings - Fork 55
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 fail if the application_name is not set properly #63
Comments
Hi @frost242, In fact, it returns I'll try to reproduce and check what we can do. |
That's it: Monitor fails
And again (the default value for on-fail is restart except for the stop action):
Then Stop fails
As @ioguix said, Failed stop = Fence:
|
Thank you for this study @blogh! Right now, I'm not sure what is the best option to this issue. The obvious one would be to relax the pg_stop function to raise |
If you set application_name to a wrong value, pgsqlms returns a "OCF_ERR_CONFIGURED" that will trigger fencing of the nodes where the service are started. It should return "OCF_ERR_ARGS" instead.
pgsqlms should return a lower level error.
The text was updated successfully, but these errors were encountered: