• Webinars
  • Docs
  • Download
  • Blogs
  • Contact Us
Show / Hide Table of Contents
  • Administrator's Guide
  • NCache Architecture
    • Cache Topologies
    • Cache Cluster
    • Local Cache
    • Cache Client
    • Client Cache
    • Data Load Balancing
    • Cache Server Backward Compatibility
    • Client Backward Compatibility
    • Eviction
    • Indexing
    • Runtime Data Sharing
    • Portable Data Types
    • Class Versioning
    • IP Binding with Multiple NICs
    • Graceful Node Down
    • Separate Cache Host Process
    • Self Healing Dynamic Clustering
  • Configuring Caches
    • Create Cache
      • Creating Local Cache
        • Create New Cache
        • Add Existing Cache
      • Creating Clustered Cache
        • Create New Cache Cluster
        • Add Existing Cache Cluster
    • Remove Cache
    • Clear Cache Contents
    • Adding Server Node in Cache Cluster
    • Removing Server Node from Cache Cluster
    • Configuring Basic Cache Settings
      • Cache Size
      • Cache Isolation Levels
      • Cache Data Expiration
      • Cache Data Format
    • Configuring Cache Cluster Settings
      • Ports
      • Operation Timeout
      • Static Replication Interval
      • Connection Retries
      • Retry Interval
    • Add Test Data to Cache
    • Deploy Providers
    • Configuring Query Indexes
    • Registering Classes for Compact Serialization
      • Registering Non-Generic Classes
      • Unregistering Non-Generic Classes
      • Registering Generic Classes
      • Registering Generic Classes Using Generic Type Handler
    • Registering Classes for Portable Data Sharing
    • Configuring Data Source Providers
      • Read-Through Provider
      • Write-Through Provider
      • Write-Through Provider for Write-Behind Operations
    • Configuring Cache Startup Loader
    • Configuring Cache Level Events
    • Configuring Cache Activity Events
    • Configuring Eviction Policy
    • Configuring Compression
    • Configuring Email Notifications
    • Binding Cluster and Client/Server IP with Multiple NICs
      • Binding Cluster with a Dedicated IP
      • Binding Client/Server with a Dedicated IP
    • Configuring Heartbeat
    • Configuring MapReduce
    • Configuring Communication Reliability
    • Auto Start Cache on Boot
    • Nagling
    • Dual Socket
    • Error Logging
    • Configuration Files
      • Client Side Configurations
        • Client Config
        • EFCaching Config
      • Server Side Configurations
        • Cache Config
        • Bridge Config
        • Security Config
      • Cache Server Configuration
  • Management Operations
    • Start Cache
    • Stop Cache
    • Restart Cache
    • Manage Cache Service on a Server Node
    • Apply Configuration
    • Hot Apply Configuration
    • Reset Configuration
    • Data Load Balancing
  • Configuring Cache Clients
    • Adding Client Node in Cluster
    • Removing Client Node from Cluster
    • Configuring Client Node Settings
    • Creating Client Cache
    • Enable Client Cache on Client Nodes
    • Disable Client Cache on Client Nodes
    • Removing Client Cache
    • Configuring Client Cache Settings
  • Configuring Security
    • Configuring Security for Cache Management
    • Configuring Security for Cache
    • Configuring Security for Client Nodes
    • Configuring Encryption for Cache
    • Configure SSL/TLS Encryption in NCache
  • Configuring Bridge for WAN Replication
    • Creating Clustered Bridge
    • Adding Clustered Caches to Bridge
    • Configuring Bridge Settings
    • Configuring Conflict Resolver
    • Changing Cache Syncronization Modes
    • Configuring Master Cache
    • Force State Transfer
    • Connect/Disconnect Cache in Bridge
    • Remove Cache from Bridge
    • Bridge Management
  • NCache on Docker
    • Using NCache Docker Images
    • Customize NCache Dockerfile
  • Monitoring NCache
    • Cache Counters
    • Monitoring Caches using NCache Manager
      • Changing Management Port of Cache Node
      • Configuring Counters to Display
      • Browse Cache Statistics
      • Cluster Health
      • Monitoring Cache Clusters using NCache Email Alerts
    • Monitoring Caches using NCache Monitor
      • Monitoring with Built-In Dashboard
      • Monitoring with Custom Dashboard
    • Monitoring Bridge using NCache Manager
    • Monitoring NCache using Windows PerfMon Tool
      • Monitoring Cache Server Counters Using PerfMon
      • Monitoring Cache Client Counters Using PerfMon
      • Monitoring Bridge Counters Using PerfMon
    • Logging in NCache
      • NCache Log Viewer
      • NCache Monitor Logging
      • Performance Counters Logging
      • Windows Event Logging
      • Email Notifications on NCache Events
      • Cache Server Logging
      • Client Side API Logging
      • Cache Event IDs
    • Troubleshooting NCache Monitoring
      • Computer Name Not Found
      • Diskperf Not Installed
      • No READ Access to the Perflib Subkeys
      • Unable to Connect to Remote Server
    • IPV6 Support
  • Upgrading NCache Versions
    • Live Upgrade NCache Version
    • Upgrade NCache Version Offline
  • Apply Windows Patches on NCache Server

Bridge Config

Note

This feature is only available in NCache Enterprise edition.

Bridge configuration file contains information regarding all registered bridges. It is installed with NCache and is located at %NCHOME%/config. bridge.ncconf is used whenever you add an existing bridge in NCache Manager. All bridge related configurations are stored in a single bridge.ncconf file. User can change the configuration of a bridge either from NCache Manger or from bridge.ncconf file.

Bridge.ncconf file is explained below:

<bridge-config config-id="b1799_AP" 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: Is the bridge identifier. Bridge cache will be known by the name you will specify here. This is the same name as you specify while initializing bridge.

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

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

Bridge-active: This 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).

Topology: Specifies which topology does the bridge follow, it can be either one of the following as provided by NCache:

  • Active-Active Topology
  • Active-Passive Topology
  • Hub-Spoke Topology
  • Star Topology

Replicator-virtual-queue-size: It is the size of a virtual queue for the replicator that replicates data from bridge to 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 purpose. NCache is providing different type of traces as shown in the above XML tag. Using these tags user can enable\disable the various traces. By default only “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 location which contains information related to the enabled traces.

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

Size: Specifies the upper limit of queue size in MB. The amount of items in 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 alias="" cache-id="demoClusteredCache" status="active" servers-list="20.200.20.38,20.200.20.29" 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="True"/>

</bridge-config>

Cache-Id: Is the cache identifier.

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

Servers-List: Server nodes comprising up of the cache clusters.

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

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

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

Clear-target-cache: If "true" it will clear the target cache on bridge service startup.

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

Back to top Copyright © 2017 Alachisoft