-
Notifications
You must be signed in to change notification settings - Fork 428
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
Add node to cluster command #228
Conversation
|
||
RES=`$NODETOOL ping` | ||
if [ "$RES" = "pong" ]; then | ||
echo "Error: Node is already running! Stop the node and delete Mnesia database directory." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would print the $MNESIA_DIR in this message also just to make it more clear what to remove.
No, this shouldn't break anything. It will just force replicating given table on the current node as you noticed.
Yes, that's a good idea. I think every module creating the mnesia table should have parameter: {local_replicas, [{TableName Type}]} Where |
any chance to finish this? |
d6ab1f8
to
dfacd68
Compare
travis is using test branch |
b6c836c
to
3aead7c
Compare
Add node to cluster command
I've introduced new commands to mongooseimctl - add_to_cluster and remove_from_cluster that simplify clustering procedure. Moreover I've added add_table_copy to all mnesia modules, it is useful when configuration changes and new modules with mnesia tables are added, then it will create replicas.
Is the add_table_copy going to break anything, should all the tables have replicas on each node?
Maybe it is a good idea to make it configurable?