-
Notifications
You must be signed in to change notification settings - Fork 9
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
starting mysql: slave is started twice in a row? #8
Comments
Hi, Regards, Yves |
OK never mind, that was a pretty stupid mistake on my part. I was referring to the mysql_prm resource agent, but it turns out I had accidentally opened the old heartbeat mysql resource. No wonder. Most pointers on the web are still to this repo, so I guess the new one is still less than obvious to find. I will use it instead. Thanks for the pointer. I'm reading through it now and can't help but notice a few things that may be incorrect. I'll attach comments as a patch: diff --git a/agents/mysql_prm b/agents/mysql_prm
|
Hi, Regards, Yves Le 2013-06-24 07:22, FrankVanDamme a écrit :
|
Not sure about this, but I'm reading through the resource script to get a better understanding of how it works and I notice this in the function "start":
on both lines 832 and 847, there is code that picks the uname of the master out of the crm's notifications ($OCF_RESKEY_CRM_meta_notify_master_uname), checks if it's a different node than the host the script is being ran on, and then sets the master to that node. There are two differences:
second time the function "start_slave" is used which also clears the
Why this difference?? Looks to me like both pieces are executed each time the script starts a mysql server.
The text was updated successfully, but these errors were encountered: