• 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

Start Cache

You can start a clustered cache on all the server nodes altogether or start it on a specific node. Please follow these steps to start the clustered cache:

Starting Cache on All Server Nodes

  • From the Cache Explorer view, right click on the cache name, which you want to start.

  • Click on the Start option in the right click context menu.

  • This starts the demoClusteredCache on all the server nodes listed under the Server Nodes tree view. Server node icon color turns to sky blue if cache is started successfully.

Starting Cache on a Particular Server Node

Using NCache Manager

  • From the Cache Explorer view, right click on the server name under Server Nodes tree node, on which you want to start the cache.

  • Click on the Start option in the right click menu, in order to start the cache.

This starts the demoClusteredCache on the selected server node. Server node icons turn to sky blue if cache is started on it.

Using Windows PowerShell

Start-Cache cmdlet enables the user to start the registered cache.

The following command starts the demoClusteredCache on server node 20.200.21.95.

Start-Cache demoClusteredCache -Server 20.200.21.95 -Port 8250

Troubleshooting

Unable to Start Cache due to Disabled Network Card

You may not be able to start the cache or clients may be unable to connect with server even on local machine. These problems arise when network card is disabled or cable is not connected.

Workaround

To resolve this problem, restart NCache service once after the network card is disabled or network cable is disconnected. Restarting NCache service will rebind it to local host rather than IP address of that machine.

Nodes Not Joining with Cluster on Cache Start

Sometimes it may be the case when you start a clustered cache, but nodes do not join with each other. It means that cluster is not formed and cache runs on each node as a standalone cache. You can use listcaches utility to confirm if the cluster is formed properly or not. When listcaches utility is used with '/a' switch, it lists all the nodes that have successfully joined the cluster. You can also use the NCache Manager "View Cluster Connectivity" GUI tool to check the node connectivity. "View Cluster Connectivity" option is available in a cluster properties and also located at NCache Manager tool bar.

Workaround

  • See that every node can be accessed from every other node participating in the clustered cache. For this you can use the 'ping' utility. If nodes are not accessible then there is some network problem and must be resolved before starting the cache.
  • Please see that the cache configuration on each node contains the correct initial hosts list. Every node participating in the clustered cache must be listed there.
  • If the initial hosts list is not correct then update the initial hosts list and restart NCache service on all nodes.
  • Restart the clustered cache.

Both Nodes in Mirror Cache Appearing as Active

Both Nodes in a Mirror Cache appear as Active in NCache Manager

On starting a mirror cache, a situation may arise where both nodes are shown as active in NCache Manager. This means that nodes could not join with each other. It is not a mirror cache cluster instead two different mirror caches are running on each node.

Workaround

To resolve this problem see how to resolve the nodes not joining issue.

Back to top Copyright © 2017 Alachisoft