Bridge Config - Geo Replication

The Bridge configuration file contains information regarding all registered bridges for geo replication. The bridge.ncconf file is installed with NCache and is used whenever you add an existing bridge in the NCache Management Center. All bridge related configurations are stored in a single bridge.ncconf file. The user can change the configuration of a bridge from the NCache Management Center or from the bridge.ncconf file.

Note

This file is located at %NCHOME%/config in Windows or opt\ncache\config in Linux.

Bridge Config Tags for Geo Replication

This file is explained below:

<bridge-config config-id="b1799_AP" auto-start="False" deployment-version="0" config-version="0" id="myBridge" bridge-nodes="20.200.20.35,20.200.20.32" num-bridge-nodes="2" bridge-active="20.200.20.35" bridge-port="10029" opt-timeout="60" src-cache="" topology="active-passive" replicator-virtual-queue-size="2048MB">

Bridge-config Id: A Bridge identifier, this Bridge cache will be known by the name you will specify here. This is the same name as you specify while initializing the bridge.

Bridge-nodes: IPs of Server nodes involved in making up this bridge.

Num-bridge-nodes: Number of servers involved in making up the bridge node.

Bridge-active: Represents the active node in the bridge.

Bridge-port: Port number on which the bridge is hosted.

Opt-timeout: (Operation Timeout) Timeout time after which the bridge will consider itself disconnected from the connected cache(s).

Replicator-virtual-queue-size: It is the size of a virtual queue for the replicator that replicates data from the bridge to the target cache.

<log enabled="True" trace-errors="True" trace-notices="False" trace-warnings="False" trace-debug="False"/>

NCache maintains a log file to write traces for information and debugging purposes. NCache provides different types of traces, as shown in the above XML tag. Using these tags user can enable\disable the various traces. By default only the “Error” trace is enabled, rest of the traces are disabled. Error trace does not affect the cache performance but for other traces, we recommend not to enable them in a production environment as they affect the performance of NCache. Here log files for each cache will be created at %NCHOME%\log-files in Windows and opt/ncache/log-files for Linux which contains information related to the enabled traces.

<queue optimized="False" size="2048"/>

Size: Specifies the upper limit of queue size in MB. The amount of items in the queue is limited by the maximum queue size and amount of free memory.

<perf-counter enabled="True"/>

Perf-counter: It is used to enable Performance counters.

<cache cache-id="demoClusteredCache.WestCoast" status="active" servers-list="20.200.20.38" bulk-operation-size="500" enable-compression="False" connection-retry-interval="3" heart-beat-enabled="True" replicator-virtual-queue-size="2048MB" is-connected="True" is-master="False"/>

</bridge-config>

Cache-Id: TCache identifier.

Status: Status of the cache connected to the bridge. It can either be active or passive depending on the selected topology.

Servers-List: Server nodes comprising the cache clusters.

Bulk-operation-size: An upper limit on the size of the bundled operation that is to be replicated on the target cache.

Enable-compression: To enable compression while sending operations on its Target Cache.

Connect-retry-interval: Specifies the interval between the two consecutive retries to connect with the target cache, if not already connected.

Heart-beat-enabled: Specifies if a heartbeat has been enabled for the cache.

Replicator-virtual-queue-size: Size of a virtual queue for the replicator that replicates data from the bridge to the target cache.

is-connected: Specifies if the cache is connected to the bridge.

See Also

Cache Config
Client Side Configurations
Security Config
Client Side Configurations