Search Results for

    Show / Hide Table of Contents

    Namespace GridGain.Core.DataCenterReplication

    Classes

    CacheDrSenderConfiguration

    Data center replication sender cache configuration.

    ClientCacheDrSenderConfiguration

    Data center replication sender cache configuration.

    DrReceiverConfiguration

    Data center replication receiver hub configuration.

    DrSenderConfiguration

    Data center replication sender hub configuration.

    DrSenderConnectionConfiguration

    Data center replication sender hub connection configuration.

    Interfaces

    ICacheDrEntry<TK, TV>

    Data center replication cache entry.

    ICacheDrEntryFilter

    Non-generic marker counterpart of ICacheDrEntryFilter<TK, TV>.

    ICacheDrEntryFilter<TK, TV>

    Data center replication sender cache filter. Prevents data center replication of cache entries which do not pass it.

    ICacheDrReceiverMetrics

    Metrics for data center replication receiver cache.

    ICacheDrSenderMetrics

    Metrics for data center replication sender cache.

    ICacheDrStateTransfer

    Data center replication state transfer descriptor.

    ICacheDrStatus

    Data center replication status.

    IDataCenterReplication

    Data Center Replication (DR) interface.

    DR is a process of transferring updates from a cache located in one topology to a cache located in another topology. Usual use case for DR is synchronizing cache state between several geographically remote topologies through WAN.

    DR operates on the following terms: Data center - particular GridGain topology with unique ID; Sender cache - cache from which data is being replicated; Receiver cache - cache which applies updates from remote data center; Sender hub - node which accumulates updates from sender data nodes and sends that to receiver hub in remote data center; receiver hub - node which receives updates from remote data center sender hub and applies them to receiver data nodes.

    Cache is considered as sender in case it has DrSenderConfiguration, and it is considered as receiver cache in case DrReceiverEnabled is true.

    Node is considered as sender hub in case it has DrSenderConfiguration, and it is considered as receiver hub in case it has DrReceiverConfiguration.

    Particular cache can be both sender and receiver at the same time. Particular node can be both sender and receiver hub and host sender/receiver caches at the same time.

    This API provides ability to manage DR process on sender cache node as well as get metrics for sender cache, receiver cache, sender hub and receiver hub.

    IDrReceiverInMetrics

    Data center replication receiver hub metrics for incoming data, i.e. data transferred from remote sender hubs to receiver hub.

    IDrReceiverOutMetrics

    Data center replication receiver hub metrics for outgoing data, i.e. data transferred from receiver hub to receiver caches.

    IDrSenderInMetrics

    Data center replication sender hub metrics for incoming data, i.e. data transferred from sender caches to sender hub.

    IDrSenderOutMetrics

    Data center replication sender hub metrics for outgoing data, i.e. data transferred from sender hub to remote receiver hubs.

    Enums

    CacheConflictMode

    Cache conflict resolver mode.

    Each cache entry has data center ID. In case cache update is performed and either old or new cache entry has data center ID which differs from local data center ID defined by DataCenterId we consider such situation as conflict.

    If both entries participating in conflict have the same data center ID (i.e. they both were replicated from the same remote data center), then GridGain can potentially resolve this conflict automatically based on entry metadata.

    But in case old and new entries have different data center IDs (i.e. in active-active scenario when cache is updated in both data centers participating in data center replication, or when cache is updated from multiple remote data centers), then explicit conflict resolution is required.

    This enumeration provides several different strategies for conflict resolution.

    CacheDrPauseReason

    Reason of data center replication pause.

    DrReceiverLoadBalancingMode

    Data center replication receiver hub load balancing mode. Determines to which receiver hub from the given remote data center the next batch will be sent from the sender hub.

    DrSenderLoadBalancingMode

    Data center replication sender hub load balancing mode. Determines to which sender hub next batch will be sent from the sender cache.

    In This Article
    Back to top © 2022 GridGain Systems, Inc. and Contributors