← ClaudeAtlas

couchbase-xdcrlisted

Design and operate Couchbase XDCR (Cross-Datacenter Replication). Use whenever the user asks about XDCR, cross-datacenter replication, multi-region replication, active-active replication, active-passive replication, XDCR topology, XDCR references, XDCR replications, XDCR filtering, conflict resolution, last-write-wins, custom conflict resolution, XDCR conflict logging (8.x), admin_xdcr_* tools, replication lag, changes_left, or 'how do I replicate data between clusters / regions.' Distinct from couchbase-app-integration (application-layer XDCR-aware patterns) and couchbase-migration-execution (one-time data migration). Use proactively for disaster recovery planning, multi-region active-active architecture, read-local write-global patterns, and XDCR performance diagnosis.
celticht32/Couchbase-Skills-for-Claude.ai · ★ 1 · AI & Automation · score 75
Install: claude install-skill celticht32/Couchbase-Skills-for-Claude.ai
# Couchbase XDCR A skill for *designing and operating* Cross-Datacenter Replication between Couchbase clusters. Distinct from: - `couchbase-app-integration` — application code patterns for XDCR-aware reads and writes - `couchbase-migration-execution` — one-time migration, not ongoing replication If the conversation is "I need data in multiple regions" or "how do I keep two clusters in sync," this is the right skill. ## When this skill applies - "How do I replicate between two clusters?" - "Active-active vs active-passive — which should I use?" - "How does conflict resolution work in XDCR?" - "How do I filter which documents get replicated?" - "How do I monitor XDCR lag?" - "XDCR replication is behind — how do I diagnose it?" - "What's the XDCR conflict log in 8.x?" ## Pick the right reference | Question | Read | |---|---| | "Active-active vs active-passive — topology decision" | `references/topology.md` | | "How do I create references and replications, filter docs, tune performance?" | `references/configuration.md` | | "Conflict resolution — LWW, custom, 8.x conflict logging" | `references/conflict-resolution.md` | | "Replication is lagging / errors / mismatched counts" | `references/troubleshooting.md` | ## Three core principles **Principle 1 — Active-active means accepting eventual consistency and conflict potential.** In active-active (bidirectional) XDCR, both clusters accept writes independently. When the same document is written on both sides before replication