-
Notifications
You must be signed in to change notification settings - Fork 138
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 _replicate
support to SG admin REST API
#1663
Comments
I don't think we can support user and role doc replication between Sync Gateways without an enhancement to manage those docs using revision trees. It would be relatively straightforward to include user and role docs in an admin _changes request, but without rev trees for those docs, we still wouldn't have a way to resolve when updates to the user docs are made in both systems, or even avoid an echo/feedback loop when an update is originally made in only one system. |
@zgramana Can you explain why SG need to replicate two or more Sync Gateway instances with each other. |
There are lots of use cases .. A simple one would be a high availability scenario with an up to date backup in a different data center. Master-master replication also an option .. One SG on west coast and one on east coast, and user devices would connect to the closest one |
_replicate
support to SG admin REST API _replicate
support to SG admin REST API
Current work is on feature/issue_1663_replicate. Status (initial implementation):
|
As an admin, I should be able to replicate two or more Sync Gateway instances with each other.
Additional criteria:
User and Role docs support.Not in initial delivery._active_tasks
.Open questions:
The text was updated successfully, but these errors were encountered: