Data Replication

<h2 id="data-replication" class="position-relative d-flex align-items-center group"> Data Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="data-replication" aria-haspopup="dialog" aria-label="Share link: Data Replication"> Share link </button> </h2><div id="headingShareModal" class="heading-share-modal" role="dialog" aria-modal="true" aria-labelledby="headingShareTitle" hidden> <div class="hsm-dialog" role="document"> <div class="hsm-header"> <h2 id="headingShareTitle" class="h6 mb-0 fw-bold">Share this section</h2> <button type="button" class="hsm-close" aria-label="Close"> </button> </div> <div class="hsm-body"> <label for="headingShareInput" class="form-label small text-muted mb-1 text-uppercase fw-bold" style="font-size: 0.7rem; letter-spacing: 0.5px;">Permalink</label> <div class="input-group mb-4 hsm-url-group"> <input id="headingShareInput" type="text" class="form-control font-monospace" readonly aria-readonly="true" style="font-size: 0.85rem;" /> <button class="btn btn-primary hsm-copy" type="button" aria-label="Copy" title="Copy"> </button> </div> <div class="small fw-bold mb-2 text-muted text-uppercase" style="font-size: 0.7rem; letter-spacing: 0.5px;">Share via</div> <div class="hsm-share-grid"> <a id="share-twitter" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Twitter </a> <a id="share-linkedin" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> LinkedIn </a> <a id="share-facebook" class="btn btn-outline-secondary w-100" target="_blank" rel="noopener noreferrer"> Facebook </a> </div> </div> </div> </div> <style> .heading-share-modal { position: fixed; inset: 0; display: flex; justify-content: center; align-items: center; background: rgba(0, 0, 0, 0.6); z-index: 1050; padding: 1rem; backdrop-filter: blur(4px); -webkit-backdrop-filter: blur(4px); } .heading-share-modal[hidden] { display: none !important; } .hsm-dialog { max-width: 420px; width: 100%; background: var(--bs-body-bg, #fff); color: var(--bs-body-color, #212529); border: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); border-radius: 1rem; box-shadow: 0 25px 50px -12px rgba(0, 0, 0, 0.25); overflow: hidden; animation: hsm-fade-in 0.2s ease-out; } @keyframes hsm-fade-in { from { opacity: 0; transform: scale(0.95); } to { opacity: 1; transform: scale(1); } } [data-bs-theme="dark"] .hsm-dialog { background: #1e293b; border-color: rgba(255,255,255,0.1); color: #f8f9fa; } .hsm-header { display: flex; justify-content: space-between; align-items: center; padding: 1rem 1.5rem; border-bottom: 1px solid var(--bs-border-color, rgba(0,0,0,0.1)); background: rgba(0,0,0,0.02); } [data-bs-theme="dark"] .hsm-header { background: rgba(255,255,255,0.02); border-color: rgba(255,255,255,0.1); } .hsm-close { background: transparent; border: none; color: inherit; opacity: 0.5; padding: 0.25rem 0.5rem; border-radius: 0.25rem; font-size: 1.2rem; line-height: 1; transition: opacity 0.2s; } .hsm-close:hover { opacity: 1; } .hsm-body { padding: 1.5rem; } .hsm-url-group { display: flex !important; align-items: stretch; } .hsm-url-group .form-control { flex: 1; min-width: 0; margin: 0; background: var(--bs-secondary-bg, #f8f9fa); border-color: var(--bs-border-color, #dee2e6); border-top-right-radius: 0; border-bottom-right-radius: 0; height: 42px; } .hsm-url-group .btn { flex: 0 0 auto; margin: 0; margin-left: -1px; border-top-left-radius: 0; border-bottom-left-radius: 0; height: 42px; display: flex; align-items: center; justify-content: center; padding: 0 1.25rem; z-index: 2; } [data-bs-theme="dark"] .hsm-url-group .form-control { background: #0f172a; border-color: #334155; color: #e2e8f0; } .hsm-share-grid { display: flex; flex-direction: column; gap: 0.5rem; } .hsm-share-grid .btn { display: flex; align-items: center; justify-content: center; font-size: 0.9rem; padding: 0.6rem; border-color: var(--bs-border-color); width: 100%; } [data-bs-theme="dark"] .hsm-share-grid .btn { color: #e2e8f0; border-color: #475569; } [data-bs-theme="dark"] .hsm-share-grid .btn:hover { background: #334155; border-color: #cbd5e1; } </style> <script> (function(){ const modal = document.getElementById('headingShareModal'); if(!modal) return; const input = modal.querySelector('#headingShareInput'); const copyBtn = modal.querySelector('.hsm-copy'); const twitter = modal.querySelector('#share-twitter'); const linkedin = modal.querySelector('#share-linkedin'); const facebook = modal.querySelector('#share-facebook'); const closeBtn = modal.querySelector('.hsm-close'); let lastFocus=null; let trapBound=false; function buildUrl(id){ return window.location.origin + window.location.pathname + '#' + id; } function isOpen(){ return !modal.hasAttribute('hidden'); } function hydrate(id){ const url=buildUrl(id); input.value=url; const enc=encodeURIComponent(url); const text=encodeURIComponent(document.title); if(twitter) twitter.href=`https://twitter.com/intent/tweet?url=${enc}&text=${text}`; if(linkedin) linkedin.href=`https://www.linkedin.com/sharing/share-offsite/?url=${enc}`; if(facebook) facebook.href=`https://www.facebook.com/sharer/sharer.php?u=${enc}`; } function openModal(id){ lastFocus=document.activeElement; hydrate(id); if(!isOpen()){ modal.removeAttribute('hidden'); } requestAnimationFrame(()=>{ input.focus(); }); trapFocus(); } function closeModal(){ if(!isOpen()) return; modal.setAttribute('hidden',''); if(lastFocus && typeof lastFocus.focus==='function') lastFocus.focus(); } function copyCurrent(){ try{ navigator.clipboard.writeText(input.value).then(()=>feedback(true),()=>fallback()); } catch(e){ fallback(); } } function fallback(){ input.select(); try{ document.execCommand('copy'); feedback(true);}catch(e){ feedback(false);} } function feedback(ok){ if(!copyBtn) return; const icon=copyBtn.querySelector('i'); if(!icon) return; const prev=copyBtn.getAttribute('data-prev')||icon.className; if(!copyBtn.getAttribute('data-prev')) copyBtn.setAttribute('data-prev',prev); icon.className= ok ? 'fa-duotone fa-clipboard-check':'fa-duotone fa-circle-exclamation'; setTimeout(()=>{ icon.className=prev; },1800); } function handleShareClick(e){ e.preventDefault(); const btn=e.currentTarget; const id=btn.getAttribute('data-share-target'); if(id) openModal(id); } function bindShareButtons(){ document.querySelectorAll('.h-share').forEach(btn=>{ if(!btn.dataset.hShareBound){ btn.addEventListener('click', handleShareClick); btn.dataset.hShareBound='1'; } }); } bindShareButtons(); if(document.readyState==='loading'){ document.addEventListener('DOMContentLoaded', bindShareButtons); } else { requestAnimationFrame(bindShareButtons); } document.addEventListener('click', function(e){ const shareBtn=e.target.closest && e.target.closest('.h-share'); if(shareBtn && !shareBtn.dataset.hShareBound){ handleShareClick.call(shareBtn, e); } }, true); document.addEventListener('click', e=>{ if(e.target===modal) closeModal(); if(e.target.closest && e.target.closest('.hsm-close')){ e.preventDefault(); closeModal(); } if(copyBtn && (e.target===copyBtn || (e.target.closest && e.target.closest('.hsm-copy')))) { e.preventDefault(); copyCurrent(); } }); document.addEventListener('keydown', e=>{ if(e.key==='Escape' && isOpen()) closeModal(); }); function trapFocus(){ if(trapBound) return; trapBound=true; modal.addEventListener('keydown', f=>{ if(f.key==='Tab' && isOpen()){ const focusable=[...modal.querySelectorAll('a[href],button,input,textarea,select,[tabindex]:not([tabindex="-1"])')].filter(el=>!el.hasAttribute('disabled')); if(!focusable.length) return; const first=focusable[0]; const last=focusable[focusable.length-1]; if(f.shiftKey && document.activeElement===first){ f.preventDefault(); last.focus(); } else if(!f.shiftKey && document.activeElement===last){ f.preventDefault(); first.focus(); } } }); } if(closeBtn) closeBtn.addEventListener('click', e=>{ e.preventDefault(); closeModal(); }); })(); </script>Data replication is the process of maintaining multiple copies of data across different nodes in a distributed graph database system. Geode provides enterprise-grade replication capabilities that ensure data availability, fault tolerance, and geographic distribution while maintaining consistency guarantees. This comprehensive guide explores replication architectures, synchronization strategies, configuration options, and operational best practices for production deployments. <h3 id="understanding-data-replication" class="position-relative d-flex align-items-center group"> Understanding Data Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="understanding-data-replication" aria-haspopup="dialog" aria-label="Share link: Understanding Data Replication"> Share link </button> </h3>Replication creates redundant copies of graph data across multiple database nodes, providing several critical benefits: <ul> <li>High Availability: If one node fails, other replicas continue serving requests</li> <li>Fault Tolerance: Data survives hardware failures and network partitions</li> <li>Read Scalability: Distribute read queries across multiple replicas</li> <li>Geographic Distribution: Place data closer to users for lower latency</li> <li>Disaster Recovery: Maintain copies in different data centers or regions</li> </ul> For graph databases, replication must handle both nodes and relationships while preserving graph structure and maintaining referential integrity across replicas. <h3 id="replication-topologies" class="position-relative d-flex align-items-center group"> Replication Topologies <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-topologies" aria-haspopup="dialog" aria-label="Share link: Replication Topologies"> Share link </button> </h3> <h4 id="master-slave-replication" class="position-relative d-flex align-items-center group"> Master-Slave Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="master-slave-replication" aria-haspopup="dialog" aria-label="Share link: Master-Slave Replication"> Share link </button> </h4>Master-slave (primary-replica) is the most common replication topology where one node accepts writes and propagates changes to read-only replicas: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: topology: "master_slave" master: # Primary node configuration node_id: "master1" listen: "0.0.0.0:3141" # Replica management replicas: - id: "replica1" address: "replica1.example.com:3141" sync_mode: "async" - id: "replica2" address: "replica2.example.com:3141" sync_mode: "async" - id: "replica3" address: "replica3.example.com:3141" sync_mode: "sync" # Replication settings replication_factor: 3 min_sync_replicas: 1 </code></pre></div>Advantages: <ul> <li>Simple to understand and operate</li> <li>Consistent write path through single master</li> <li>Read scaling through multiple replicas</li> <li>Clear failure modes</li> </ul> Disadvantages: <ul> <li>Single point of failure for writes</li> <li>Limited write scalability</li> <li>Master can become bottleneck</li> </ul> Use Cases: <ul> <li>Read-heavy workloads</li> <li>Applications requiring strong consistency</li> <li>Traditional OLTP systems</li> </ul> <h4 id="multi-master-replication" class="position-relative d-flex align-items-center group"> Multi-Master Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="multi-master-replication" aria-haspopup="dialog" aria-label="Share link: Multi-Master Replication"> Share link </button> </h4>Multi-master replication allows writes on any node, with changes propagated to all other masters: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: topology: "multi_master" cluster: nodes: - id: "master1" address: "master1.example.com:3141" region: "us-east" - id: "master2" address: "master2.example.com:3141" region: "us-west" - id: "master3" address: "master3.example.com:3141" region: "eu-west" # Conflict resolution conflict_resolution: strategy: "last_write_wins" timestamp_source: "hybrid_logical_clock" # Replication mode replication_mode: "asynchronous" </code></pre></div>Advantages: <ul> <li>No single point of failure</li> <li>Write scalability across multiple nodes</li> <li>Geographic distribution of write capacity</li> <li>Lower write latency for distributed users</li> </ul> Disadvantages: <ul> <li>Complex conflict resolution</li> <li>Eventual consistency challenges</li> <li>More complex failure scenarios</li> </ul> Use Cases: <ul> <li>Globally distributed applications</li> <li>High write throughput requirements</li> <li>Multi-region deployments</li> </ul> <h4 id="chain-replication" class="position-relative d-flex align-items-center group"> Chain Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="chain-replication" aria-haspopup="dialog" aria-label="Share link: Chain Replication"> Share link </button> </h4>Chain replication organizes replicas in a linear chain for efficient propagation: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: topology: "chain" chain: # Head node receives writes head: "node1.example.com:3141" # Chain members members: - "node2.example.com:3141" - "node3.example.com:3141" # Tail node confirms commits tail: "node4.example.com:3141" # Chain configuration chain_replication: # Acknowledge after tail confirms ack_mode: "tail" # Propagation timeout propagation_timeout_ms: 1000 </code></pre></div>Advantages: <ul> <li>Strong consistency guarantees</li> <li>Efficient bandwidth usage</li> <li>Simple failure recovery</li> </ul> Disadvantages: <ul> <li>Higher latency for acknowledgments</li> <li>Chain length limits scalability</li> <li>Head node can become bottleneck</li> </ul> Use Cases: <ul> <li>Strong consistency requirements</li> <li>Linear data flow patterns</li> <li>Storage systems requiring durability</li> </ul> <h3 id="synchronization-strategies" class="position-relative d-flex align-items-center group"> Synchronization Strategies <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="synchronization-strategies" aria-haspopup="dialog" aria-label="Share link: Synchronization Strategies"> Share link </button> </h3> <h4 id="synchronous-replication" class="position-relative d-flex align-items-center group"> Synchronous Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="synchronous-replication" aria-haspopup="dialog" aria-label="Share link: Synchronous Replication"> Share link </button> </h4>Synchronous replication waits for replicas to acknowledge writes before returning success: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: synchronous: # Require acknowledgment from replicas enabled: true # Wait for N replicas required_acks: 2 # Acknowledgment timeout timeout_ms: 5000 # Fail if timeout exceeded on_timeout: "fail" # Durability guarantees durability: fsync: true write_ahead_log: true </code></pre></div>Transaction Example: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Synchronous write with guaranteed replication BEGIN TRANSACTION WITH DURABILITY LEVEL SYNCHRONOUS; CREATE (u:User { id: $user_id, name: $name, email: $email, created: current_timestamp() }); -- This commit waits for replica acknowledgments COMMIT; </code></pre></div>Characteristics: <ul> <li>Latency: Higher due to network round-trips</li> <li>Consistency: Strong consistency guarantees</li> <li>Availability: Lower (requires replica acknowledgment)</li> <li>Durability: Maximum (data on multiple nodes before confirmation)</li> </ul> <h4 id="asynchronous-replication" class="position-relative d-flex align-items-center group"> Asynchronous Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="asynchronous-replication" aria-haspopup="dialog" aria-label="Share link: Asynchronous Replication"> Share link </button> </h4>Asynchronous replication returns success immediately and propagates changes in the background: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: asynchronous: enabled: true # Background replication background: # Replication workers worker_threads: 4 # Batch size for efficiency batch_size: 100 # Maximum batch delay max_delay_ms: 100 # Replication lag monitoring lag_monitoring: enabled: true warn_threshold_ms: 1000 critical_threshold_ms: 5000 </code></pre></div>Characteristics: <ul> <li>Latency: Low (immediate return)</li> <li>Consistency: Eventual consistency</li> <li>Availability: High (no dependency on replicas)</li> <li>Durability: Lower (potential data loss if primary fails)</li> </ul> <h4 id="semi-synchronous-replication" class="position-relative d-flex align-items-center group"> Semi-Synchronous Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="semi-synchronous-replication" aria-haspopup="dialog" aria-label="Share link: Semi-Synchronous Replication"> Share link </button> </h4>Semi-synchronous replication waits for at least one replica while allowing others to lag: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: semi_synchronous: enabled: true # Wait for at least one replica min_sync_replicas: 1 # Timeout for synchronous replica sync_timeout_ms: 1000 # Fall back to async if timeout fallback_mode: "asynchronous" # Promote async replicas if needed auto_promote: true </code></pre></div>Characteristics: <ul> <li>Balance between performance and durability</li> <li>Guarantees at least one replica has data</li> <li>Better availability than fully synchronous</li> <li>Lower latency than fully synchronous</li> </ul> <h3 id="replication-configuration" class="position-relative d-flex align-items-center group"> Replication Configuration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-configuration" aria-haspopup="dialog" aria-label="Share link: Replication Configuration"> Share link </button> </h3> <h4 id="basic-replication-setup" class="position-relative d-flex align-items-center group"> Basic Replication Setup <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="basic-replication-setup" aria-haspopup="dialog" aria-label="Share link: Basic Replication Setup"> Share link </button> </h4>Configure a master with two replicas: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"># master-config.yaml replication: enabled: true role: "master" # Replication settings replication_factor: 3 sync_mode: "semi_synchronous" min_sync_replicas: 1 # Write-ahead log for replication wal: enabled: true directory: "/var/lib/geode/wal" max_size_gb: 10 retention_hours: 24 # Replica configuration replicas: - name: "replica1" address: "replica1.example.com:3141" sync_mode: "sync" - name: "replica2" address: "replica2.example.com:3141" sync_mode: "async" # Replication monitoring monitoring: lag_threshold_ms: 1000 health_check_interval_ms: 5000 </code></pre></div> <h4 id="replica-configuration" class="position-relative d-flex align-items-center group"> Replica Configuration <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replica-configuration" aria-haspopup="dialog" aria-label="Share link: Replica Configuration"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"># replica-config.yaml replication: enabled: true role: "replica" # Master connection master: address: "master.example.com:3141" connection: retry_interval_ms: 1000 max_retries: 10 timeout_ms: 30000 # Replica settings replica: # Read-only mode read_only: true # Apply replication stream apply_lag_target_ms: 100 # Buffer for replication data buffer_size_mb: 256 # Failover configuration failover: # Enable automatic promotion auto_promote: true # Promotion criteria criteria: max_lag_ms: 5000 min_uptime_seconds: 300 </code></pre></div> <h3 id="replication-operations" class="position-relative d-flex align-items-center group"> Replication Operations <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-operations" aria-haspopup="dialog" aria-label="Share link: Replication Operations"> Share link </button> </h3> <h4 id="setting-up-replication" class="position-relative d-flex align-items-center group"> Setting Up Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="setting-up-replication" aria-haspopup="dialog" aria-label="Share link: Setting Up Replication"> Share link </button> </h4>Initialize replication on a running system: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Configure master node geode replication init-master \ --listen=0.0.0.0:3141 \ --wal-dir=/var/lib/geode/wal \ --replication-factor=3 # Add replica geode replication add-replica \ --name=replica1 \ --address=replica1.example.com:3141 \ --sync-mode=async # Start replica and connect to master geode replication init-replica \ --master=master.example.com:3141 \ --replica-id=replica1 </code></pre></div> <h4 id="managing-replicas" class="position-relative d-flex align-items-center group"> Managing Replicas <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="managing-replicas" aria-haspopup="dialog" aria-label="Share link: Managing Replicas"> Share link </button> </h4>Monitor and manage replication: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># View replication status geode replication status # Check replication lag geode replication lag --all # Pause replication on replica geode replication pause --replica=replica1 # Resume replication geode replication resume --replica=replica1 # Rebuild replica from snapshot geode replication rebuild \ --replica=replica1 \ --snapshot=latest # Remove replica geode replication remove-replica \ --name=replica1 \ --force </code></pre></div> <h4 id="failover-and-promotion" class="position-relative d-flex align-items-center group"> Failover and Promotion <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="failover-and-promotion" aria-haspopup="dialog" aria-label="Share link: Failover and Promotion"> Share link </button> </h4>Handle master failures: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Manual failover to replica geode replication promote \ --replica=replica1 \ --force # List promotion candidates geode replication promotion-candidates # Configure automatic failover geode replication configure-failover \ --auto-promote=true \ --max-lag=5000ms \ --timeout=30s </code></pre></div> <h3 id="replication-monitoring" class="position-relative d-flex align-items-center group"> Replication Monitoring <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-monitoring" aria-haspopup="dialog" aria-label="Share link: Replication Monitoring"> Share link </button> </h3> <h4 id="replication-metrics" class="position-relative d-flex align-items-center group"> Replication Metrics <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-metrics" aria-haspopup="dialog" aria-label="Share link: Replication Metrics"> Share link </button> </h4>Track replication health and performance: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">monitoring: replication: enabled: true metrics: # Replication lag in milliseconds - name: "replication_lag_ms" type: "gauge" labels: ["replica_id"] # Bytes replicated per second - name: "replication_throughput_bytes" type: "gauge" labels: ["replica_id"] # Replication operations - name: "replication_ops_total" type: "counter" labels: ["replica_id", "operation"] # Replication errors - name: "replication_errors_total" type: "counter" labels: ["replica_id", "error_type"] # Export to Prometheus prometheus: enabled: true port: 9090 </code></pre></div>Key metrics: <ul> <li><code>geode_replication_lag_ms</code>: Time lag between master and replica</li> <li><code>geode_replication_throughput_bytes_per_sec</code>: Replication data rate</li> <li><code>geode_replication_queue_size</code>: Pending replication operations</li> <li><code>geode_replication_connected_replicas</code>: Number of connected replicas</li> <li><code>geode_replication_lag_seconds_p99</code>: 99th percentile lag</li> </ul> <h4 id="diagnostic-queries" class="position-relative d-flex align-items-center group"> Diagnostic Queries <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="diagnostic-queries" aria-haspopup="dialog" aria-label="Share link: Diagnostic Queries"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-gql" data-lang="gql">-- Check replication status CALL dbms.replication.status() YIELD replica_id, lag_ms, state, last_transaction; -- View replication topology CALL dbms.replication.topology() YIELD role, node_id, replicas; -- Get replication statistics CALL dbms.replication.stats() YIELD bytes_replicated, ops_per_second, avg_lag_ms; </code></pre></div> <h3 id="advanced-replication-features" class="position-relative d-flex align-items-center group"> Advanced Replication Features <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="advanced-replication-features" aria-haspopup="dialog" aria-label="Share link: Advanced Replication Features"> Share link </button> </h3> <h4 id="selective-replication" class="position-relative d-flex align-items-center group"> Selective Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="selective-replication" aria-haspopup="dialog" aria-label="Share link: Selective Replication"> Share link </button> </h4>Replicate only specific graph elements: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: selective: enabled: true # Replicate specific labels labels: include: ["User", "Product", "Order"] exclude: ["TempData", "SessionInfo"] # Replicate by property filters: - label: "User" property: "region" values: ["US", "EU"] - label: "Order" property: "status" values: ["completed", "shipped"] </code></pre></div> <h4 id="cascading-replication" class="position-relative d-flex align-items-center group"> Cascading Replication <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="cascading-replication" aria-haspopup="dialog" aria-label="Share link: Cascading Replication"> Share link </button> </h4>Create replication hierarchies: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml">replication: cascading: enabled: true # Tier 1: Primary to regional masters tier1: - replica: "us_master" cascade: true - replica: "eu_master" cascade: true # Tier 2: Regional masters to local replicas tier2: us_master: replicas: ["us_replica1", "us_replica2"] eu_master: replicas: ["eu_replica1", "eu_replica2"] </code></pre></div> <h4 id="point-in-time-recovery" class="position-relative d-flex align-items-center group"> Point-in-Time Recovery <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="point-in-time-recovery" aria-haspopup="dialog" aria-label="Share link: Point-in-Time Recovery"> Share link </button> </h4>Replay replication stream to specific point in time: <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Create PITR snapshot geode replication snapshot \ --name=before_migration \ --timestamp="2024-01-24T10:00:00Z" # Restore to point in time geode replication restore \ --snapshot=before_migration \ --target-replica=recovery_node # List available snapshots geode replication snapshots --list </code></pre></div> <h3 id="best-practices" class="position-relative d-flex align-items-center group"> Best Practices <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="best-practices" aria-haspopup="dialog" aria-label="Share link: Best Practices"> Share link </button> </h3> <h4 id="replication-strategy-selection" class="position-relative d-flex align-items-center group"> Replication Strategy Selection <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="replication-strategy-selection" aria-haspopup="dialog" aria-label="Share link: Replication Strategy Selection"> Share link </button> </h4><ol> <li> Synchronous Replication: Critical data requiring zero data loss (financial transactions, audit logs) </li> <li> Asynchronous Replication: High-throughput workloads where eventual consistency is acceptable (analytics, caching) </li> <li> Semi-Synchronous: Balanced approach for most production workloads </li> <li> Multi-Master: Globally distributed applications with regional write requirements </li> </ol> <h4 id="configuration-guidelines" class="position-relative d-flex align-items-center group"> Configuration Guidelines <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="configuration-guidelines" aria-haspopup="dialog" aria-label="Share link: Configuration Guidelines"> Share link </button> </h4><ul> <li>Replication Factor: Use 3 replicas for production (tolerates 1-2 node failures)</li> <li>Minimum Sync Replicas: Set to 1 for semi-synchronous replication</li> <li>Lag Thresholds: Alert at 1 second lag, escalate at 5 seconds</li> <li>WAL Retention: Keep 24-48 hours for recovery scenarios</li> <li>Network Bandwidth: Provision 2-3x peak write throughput for replication</li> </ul> <h4 id="operational-best-practices" class="position-relative d-flex align-items-center group"> Operational Best Practices <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="operational-best-practices" aria-haspopup="dialog" aria-label="Share link: Operational Best Practices"> Share link </button> </h4><ul> <li>Monitor replication lag continuously</li> <li>Test failover procedures regularly</li> <li>Use geographically distributed replicas for disaster recovery</li> <li>Automate replica promotion for high availability</li> <li>Document replication topology and dependencies</li> <li>Implement gradual rollout for replication configuration changes</li> </ul> <h3 id="troubleshooting" class="position-relative d-flex align-items-center group"> Troubleshooting <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="troubleshooting" aria-haspopup="dialog" aria-label="Share link: Troubleshooting"> Share link </button> </h3> <h4 id="common-replication-issues" class="position-relative d-flex align-items-center group"> Common Replication Issues <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="common-replication-issues" aria-haspopup="dialog" aria-label="Share link: Common Replication Issues"> Share link </button> </h4>High Replication Lag: Replicas falling behind master. Solution: Increase network bandwidth, optimize replica hardware, reduce write load, or add more replica workers. Replication Broken: Replica disconnected from master. Solution: Check network connectivity, verify credentials, examine WAL availability, consider rebuilding replica. Replication Conflicts: Multi-master conflicts requiring resolution. Solution: Review conflict resolution strategy, analyze conflicting transactions, implement application-level conflict handling. Disk Space: WAL consuming too much disk space. Solution: Reduce WAL retention, increase replica synchronization frequency, add disk capacity. <h4 id="diagnostic-commands" class="position-relative d-flex align-items-center group"> Diagnostic Commands <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="diagnostic-commands" aria-haspopup="dialog" aria-label="Share link: Diagnostic Commands"> Share link </button> </h4><div class="highlight"><pre tabindex="0" class="chroma"><code class="language-bash" data-lang="bash"># Check replication connectivity geode replication ping --all # Analyze replication lag geode replication analyze-lag \ --window=1h \ --show-peaks # Verify replication consistency geode replication verify-consistency \ --replica=replica1 \ --sample-rate=0.01 # Export replication logs geode replication export-logs \ --replica=replica1 \ --output=replication-logs.json # Test failover procedure geode replication test-failover \ --dry-run \ --target-replica=replica1 </code></pre></div> <h3 id="related-topics" class="position-relative d-flex align-items-center group"> Related Topics <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="related-topics" aria-haspopup="dialog" aria-label="Share link: Related Topics"> Share link </button> </h3><ul> <li><a href="/tags/clustering/" >Clustering</a> - Database clustering and multi-node deployment</li> <li><a href="/tags/consistency/" >Consistency</a> - Data consistency models</li> <li><a href="/tags/high-availability/" >High Availability</a> - Building resilient systems</li> <li><a href="/tags/backup/" >Backup and Recovery</a> - Backup and recovery strategies</li> <li><a href="/tags/scalability/" >Scalability</a> - Horizontal scaling approaches</li> <li><a href="/tags/distributed-systems/" >Distributed Systems</a> - Distributed systems architecture</li> </ul> <h3 id="further-reading" class="position-relative d-flex align-items-center group"> Further Reading <button type="button" class="h-share btn btn-link p-0 text-decoration-none link-secondary opacity-50 hover-opacity-100 transition-all ms-1" data-share-target="further-reading" aria-haspopup="dialog" aria-label="Share link: Further Reading"> Share link </button> </h3><ul> <li><a href="/docs/architecture/distributed-architecture/" >Distributed Architecture</a> - Distributed systems overview</li> <li><a href="/guides/high-availability/" >High Availability Guide</a> - Building resilient systems</li> <li><a href="/guides/backup-restore/" >Backup and Restore</a> - Data protection guide</li> <li><a href="/docs/guides/multi-datacenter/" >Multi-Datacenter Deployment</a> - Geographic distribution</li> </ul>

Popular

Related Articles

High Availability Guide