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

Clarify documentation on master-slave setup #110

Open
mbi opened this issue Jul 29, 2017 · 0 comments
Open

Clarify documentation on master-slave setup #110

mbi opened this issue Jul 29, 2017 · 0 comments

Comments

@mbi
Copy link

mbi commented Jul 29, 2017

With persistence in use, if the container is stopped and started, for the container continue to function as a slave you need to ensure that REPLICATION_MODE=slave is defined in the containers environment. In the absense of which the slave configuration will be turned off and the node will allow writing to it while having the last synced data from the master.

Is this the recommended way of promoting a slave to a master, in case of failure of the master node?
I.e.:

  • Run both the master and the slave with persistence
  • In case of failure of the master, restart the slave without REPLICATION_MODE
  • Add a new slave to point the newly promoted master

Thank you.

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

1 participant