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

resource receiving stop signal at different times #1305

Open
nanatsch opened this issue Jan 18, 2024 · 1 comment
Open

resource receiving stop signal at different times #1305

nanatsch opened this issue Jan 18, 2024 · 1 comment

Comments

@nanatsch
Copy link

Hello!
I made a 2 nodes cluster with resource clone-DB, then I use cmd "crm resource stop clone-DB" to stop database service when the database is running TPCC test with more than 20 concurrent transactions. The database log shows it receives stop request at different times (about 40s interval), again the pacemaker log (te_rsc_command) shows it initiating stop operation DB_stop_0 on node1 and node2 at different times. Does this relevant to some internal mechanisms of pacemaker? or just relevant to database or even hardware?
Pacemaker version 2.0.3
crm version 3.0.1

@liangxin1300
Copy link
Collaborator

I guess pacemaker failed to stop your resource and tried to stop it again, under the failure-counts?

Please see https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/#failure-counts
And https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/#failure-response

BTW, you can raise your concerns about pacemaker to [email protected]

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

2 participants