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

Application SysAdmin Guide - "How to reset the cluster without re-installation" #3

Open
norton opened this issue Mar 25, 2011 · 0 comments
Milestone

Comments

@norton
Copy link
Contributor

norton commented Mar 25, 2011

Add new section to describe the steps for resetting a cluster without re-installation.

(2011/03/25 11:34), Joseph Wayne Norton wrote:

Miyasaka-san -

Try the following order of operations:

  1. hibari/bin/hibari stop
  2. Check by "ps -Alf | grep beam.smp"

If anything is running, "killall -9 beam.smp"

If you want to be really safe, "killall -9 epmd"
... but not recommended unless you know that hibari is the only Erlang
virtual machine running on the host.

  1. Delete files hibari/data/brick/*
  2. Delete files hibari/Schema.local
  3. hibari/bin/hibari start
  4. hibari/bin/hibari status

If status is NOT OK, then check logs, etc.

  1. do bootstrap operations

NOTE: All brick nodes must be running before doing bootstrap operations.
NOTE: All brick nodes must have same cookie before doing bootstrap
operations.

If status is NOT OK, then check logs, etc.

If problem cannot be resolved, please do a FULL re-install and then
repeat the above procedure once and then repeat again to make sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants