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

Dealing with node failure #23

Open
sargun opened this issue Mar 7, 2016 · 1 comment
Open

Dealing with node failure #23

sargun opened this issue Mar 7, 2016 · 1 comment

Comments

@sargun
Copy link

sargun commented Mar 7, 2016

How do you deal with node failure? How do you retire a node, if you want to remove it from the cluster?

@SergejJurecko
Copy link
Contributor

Once you have the replacement ready (new hardware/vm), create a backup from an existing node. Put the backup lmdb file in the data directory. It is easiest to start the new node with the same vm.args/app.config as the old node. If you do so it will start working straight away. This works if you can keep the same node name and IP/domain.

If you don't have the same IP/domain. Start actordb on the new node (with the lmdb file and correct vm.args/app.config), then run SQL UPDATE statement through actordb_console (connected to one of the old unchanged nodes) to change the name to the new node.

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