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
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.
How do you deal with node failure? How do you retire a node, if you want to remove it from the cluster?
The text was updated successfully, but these errors were encountered: