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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: