github-starred/couchdb-best-practices
2
0
Fork 0
mirror of https://github.com/jo/couchdb-best-practices.git synced 2026-05-15 14:16:00 -06:00
Code Issues 232 Projects Releases Packages Wiki Activity Actions

[GH-ISSUE #63] Add some documentation for multi-master replication setups #667

New issue
Open
opened 2026-04-18 22:01:04 -06:00 by gitea-mirror · 0 comments
gitea-mirror commented 2026-04-18 22:01:04 -06:00
Owner
Copy link

Originally created by @krgn on GitHub (Aug 17, 2015).
Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/63

It would be really useful to document multi-master replication setups. In particular, what happens with circular replications between a set of hosts (i.e. nothing :)). Also, an interesting question to cover is how document updates to the same revision of a doc on different machines would play out in practice.

I would do it, but I don't have the answers :)

Originally created by @krgn on GitHub (Aug 17, 2015). Original GitHub issue: https://github.com/jo/couchdb-best-practices/issues/63 It would be really useful to document multi-master replication setups. In particular, what happens with circular replications between a set of hosts (i.e. nothing :)). Also, an interesting question to cover is how document updates to the same revision of a doc on different machines would play out in practice. I would do it, but I don't have the answers :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
gh-pages
No results found.
Labels
Clear labels   
pull-request

Mirrored from GitHub Pull Request

  
question
No labels
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/couchdb-best-practices#667
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?