-
Notifications
You must be signed in to change notification settings - Fork 473
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 the support of the namespace replication #1776
Conversation
It just come to me that if we firstly set |
Good point, we should remove the DB key if this option switches from yes to no. But this may introduce another issue if the slave enables this configuration. So I think we can disallow changing it to |
663353c
to
4391ba4
Compare
This PR implements the namespace replication between master and slaves, the detailed design is inside #1720. We added a new configuration
repl-namespace-enabled
to turn on/off this feature and it's disabled by default.If
repl-namespace-enabled
is set tono
, it behaves the same as the previous. All namespace configurations are stored in the configuration file.if
repl-namespace-enabled
is set toyes
, all namespace configurations will be removed from the configuration file, stored in DB, and then propagated to slaves. If the namespace has already existed in the slave, it will be overwritten by the master. Another significant change is that slaves cannot change namespaces if the replication is enabled.This closes #1720