Skip to content

DOC-13427 Update Eventing Note in XDCR Active-Active SGW doc #3844

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Aug 4, 2025
Merged

DOC-13427 Update Eventing Note in XDCR Active-Active SGW doc #3844

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8080ba1
added-content
rao-shwe Jul 31, 2025
97fe71c
minor-edit
rao-shwe Aug 1, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions modules/learn/pages/clusters-and-availability/xdcr-active-active-sgw.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,10 @@ This is due to an internal limitation of managing extended attributes in a docum
If you try to use the feature _XDCR Active-Active with Sync Gateway_ when you have more than 10 user xattrs in your document, the XDCR replication **silently skips** replicating that document.
As a result, the data in the replication-skipped document will not be consistent between the target and source clusters.
The only way you will know this skip occured is because the Prometheus stat `subdoc_cmd_docs_skipped` will be incremented and the document will _not_ be consistent between the target and source.
* Eventing Service cannot be used with Sync Gateway in bi-directional XDCR.
If used with the _Sync Gateway in a bi-directional, active-active XDCR_ environment, the updates of Eventing Service metadata in the source and the target clusters causes XDCR to ping-pong and never stop replicating.
One-way replication is possible.

* If you use Eventing service functions that update documents in XDCR-replicated buckets (Eventing source bucket mutations), ensure your functions do not cause continuous replication loops.
In bi-directional active-active XDCR environments, Eventing functions that trigger document updates can lead to "ping-pong" replication unless you implement logic to prevent infinite loops.
Always add safeguards to avoid redundant updates and unwanted replication behavior in bi-directional setups. For more information, see xref:sync-gateway:xdcr-active-active-eventing.adoc[XDCR Active-Active and Eventing].
====

You can configure XDCR Active-Active with Sync Gateway for XDCR-Mobile interoperability using one of the following methods:
Expand Down