MySQL Forums
Forum List  »  NDB clusters

Re: MCMD Agent Trouble
Posted by: Thomas Nielsen
Date: June 08, 2018 03:36AM


From the limited information provided it appears mcmds repostitory has become corrupt when mcmd terminated. This can happen when forcefully stopping mcmd (or the host) while it is writing to its repository, leaving a partially written file on disk.

In a single host setup you should restore from your latest agent backup:

In a multi host setup, you have more durability, and you let mcmd recover automatically by pulling the data from one of the other mcmds in your management site. Follow the procedure for restoring from an agent backup, but skip the steps copying from the backup folder and restart the mcmd with an empty repository.

You can of course start your cluster without MCM if you want.

If you didn't create an agent backup, your only option is using "import cluster" to import your cluster into MCM after starting it manually. Check your mcmd.log to see the exact command lines MCM used to start the cluster processes, as this will help significantly during import.


Options: ReplyQuote

Written By
June 07, 2018 10:00AM
Re: MCMD Agent Trouble
June 08, 2018 03:36AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.