Alachisoft NCache 4.1 - Online Documentation

Configure Clustered Cache

 
NCache Manager provides ability to change the configuration of Clustered Caches whether Replicated, Partitioned or Partitioned Replica . To change the configuration of a cluster, click the cluster from 'NCache Management' tree. Cluster View will appear in the right pane. This view provides configuration options for the selected cluster.
After Configuring Cache you have to Apply Configurations as well. See how to apply.
 
Cluster view consists of following tabs:
 
 
 
Main Tab
 
 
 
 
  • Clustered Cache Name: A unique identifier for the cluster. For a clustered cache, the identifier has to be unique on all the nodes that are part of it.
  • Clustered Cache Type: Indicates a clustering scheme.
  • Storage Type: Specifies the storage options for the primary cache.
  • Cache Max. Size: Specifies an upper limit on the size of the cache.
  • Isolation Level: Specify application isolation level. A High isolation level implies that the Cache runs in NCache service's process whereas a Low level implies that Cache is InProc to the applications. An OutProc cache can be shared between different applications on the same node. Moreover, an isolated cache's lifetime is explicitly controlled by applications like NCache Manager, Cmd Tools or API's.
  • Auto Start Cache: Using “Auto Start Cache” option, user can set/reset cache starting operation on service start up.
  • Now auto start cache delay time can also be added. To add delay time you have to add following tag in NCache service config file. Value is specified in minutes.
  <add key="NCacheSrver.AutoStartDelay" value="5"/>
  • Whenever NCache service will be restarted, all caches which are set to auto start will automatically start after specified delay time interval.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Cluster Settings Tab
 
 
 
  • Cluster Port: The port on which cluster communicates.
  • Port Range: Specifies port range for each node in the cluster.
  • Operation timeout (sec.): The maximum time in seconds during which a clustered operation must be completed, otherwise the operation will fail.
  • Statistic replication interval(sec's.): The time interval in seconds after which a node sends its statistics to all the other nodes in the cluster.
  • Use heart beat: When this option is enabled, a node of a cluster will send heart beats to other nodes to show that it is alive, if inactive for specified duration of time. Therefore, if live nodes do not receive heart beats from any idle node after specific duration, they will consider it dead.
  • Retry Interval (sec): It is the time interval between the two successive retries.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Policies Tab
 
 
 
 
  • Eviction Policy: Specifies the eviction policy to determine which items to be removed from cache, if it is full to accommodate new items.
  • Default Priority: Default priority that is associated with an item if no priority is specified for that item in case of priority based eviction.
  • Eviction Percentage: Specifies the percentage of items to be removed on each eviction.
  • Clean Interval (sec.): The periodic interval after which expired items are removed from the cache.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
 
Auto Load Balancing (This feature is not available in NCache Express)
 
  • Auto Load Balancing option is available for partitioned caches only.
 
 
 
  • Enable Auto Load Balancing : To balance data load among all nodes of a cluster automatically after specified period of time, check this option.
  • Balancing Threshold: Threshold is percentage data above average data size per node. Specify threshold value after which automatic balancing task should be started.
  • Balancing Interval (sec): This is periodic interval after which auto load balancing task will be initiated.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Compact Serialization Tab (This feature is not available in NCache Express)
 
 
 
 
  • Add Types : Opens an assembly browser that lets you select the assembly file that contains your compact serialized application objects.
  • Remove : Removes selected types from the registered types list.
  • Add <T> : Adds argument for generic types.
  • Generic Types Handler : Adds generic Types at once.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Query Indexes Tab (This feature is not available in NCache Express)
 
 
Using Add button select the classes and their attributes you want to index.
 
 
 
 
Selected assembly displays the list of classes and their attributes on which indexes are required. You can add/remove classes and objects to index the attributes from here.
 
Backing Source Tab (This feature is not available in NCache Express)
 
 
 
 
Backing Source tab gives option to enable multiple Read-through and Write-through providers on clustered cache.
  • A cache for which a read-through is enabled can automatically load requested items from data source as if the data is already in the cache. For multiple data sources, multiple read-through providers can be added against a cache. In case of multiple read-through providers you can set a default read-through provider for a cache using the Set as Default button.
 
Note: Read-Through must be enabled for Cache Forwarding.
  • A write-through or write-behind enabled cache writes updates back to the data source. You can specify multiple write-through providers in case of multiple data sources and can set one of them as a default write-through provider using Set as Default button.
 
  • After enabling providers for cache you can add providers using Add button. By single click on Add button, "Add New Provider" wizard will appear requiring provider information as shown in the figure.
  • Provider Name: Provider name identifies a unique provider, so for every Read Thru/Write Thru provider, an exclusive provider name must be given.
  • Assembly Name: Browse the assembly name that contains implementation for IReadThruProvider/IWriteThruProvider interface.
  • Class Name: Select the class name from the list that implements IReadThruProvider/IWriteThruProvider interfaces.
  • You can also specify additional configuration parameters that will be passed to the Start method of IReadThruProvider/ IWriteThruProvider.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
 
 
 
  • You can edit or remove the provider from the list through Edit and Remove button.
  • Deploy Provider: Deploy Provider allow you to copy/update provider assemblies to the cache servers. Use this button to select appropriate assemblies for deployment.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Cache Loader Tab
 
 
 
 
  • Enable Cache Startup Loader: A cache startup loader can automatically loads data specified by the user in the class that implements ICacheLoader interface.
  • Assembly Name: Full path of the assembly that contains implementation for ICacheLoader interface.
  • Class Name: Name of the class that implements ICacheLoader interface.
  • You may specify additional configuration parameters that will be passed to the Start method of ICacheLoader.
  • No. of Retries: Specifies the number of attempts the cache loader will try to load data, if it fails to load data on previous attempt.
  • Retry Interval(sec.): The time interval in seconds between two retry attempts of cache loader.
  • Deploy Cache Loader: Deploy Cache Loader allow you to copy the cache loader assembly to the cache server. Use this button to select the appropriate assembly for deployment.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Data Sharing Tab
 
 
 
 
  • Add Shared Types: Opens an assembly browser that lets you select the assembly/jar files that contains the classes you want to share in cache.
  • Remove: It will remove the particular Shared Type/Class from the list.
  • Import/Export: Shared Type configurations can be import and export in XML file for later use.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Conflict Resolver
 
 
 
 
There could be a situation, when a bridge can try to replicate an operation for a key that already exists in the cache.  Conflict Resolver is introduced to resolve the conflict between existing operations and operation replicated from bridge to cache. It decides which key to apply on the cache depending upon defined rules. By default the decision will be made on “Time Based” rule, which keeps the latest key in cache. Users can also define their own rules for conflict resolver.
 
 
Options Tab
 
 
 
 
  • Item add notification: Specifies whether to notify when an item is added to the cache or not.
  • Item remove notification: Indicates whether to notify when an item is removed from the cache or not
  • Item update notification: Denotes whether to notify when an item is updated or not
  • Cache clear notification: Specifies whether to notify when cache is cleared or not.
  • Enable performance counters: Identifies whether performance counters are enabled or not. Performance counters are used to show statistics of the cache.
  • Enable Compression: Shows compression is enabled or not. If enabled, items having size greater than the specified threshold will be compressed.
  • Use Custom SQL Notification Mode: It allows you to create your own SQL notification service and queue. Otherwise default service and queue will be created and used at run time.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
Security
 
 
 
 
Administrator and NCache manager can configure API level security for a cache. Each cache will have its own API security configurations independent of other caches and users. Cache API security configurations will be saved in config.ncconf against each cache. NCache Manager provides the above wizard for configuring API security for caches.
 
 
 
 
 
Now data can be sent and stored in cache in encrypted form. 3DES encryption algorithm is used to secure data, it uses three successevie iterations of DES. User can enable encryption by selecting "Enable" option and then providing Key value of length 24.
After configuring you have to Apply Configurations as well. See how to apply.
 
 
 
Alerts
 
 
 
 
Using Alerts tab view you can specify different parameters for email notifications.
 
  • Enable Email Notifications: Email notifications will be enabled by selecting an Enable Email Notifications check box .
  • Sender Email: Enter the sender email Id.
  • SMTP Server: Specify the SMTP server name.
  • Port: Default port of a server is 25 but you can change it.
  • SSL Required: Secure Server Layer if enabled then email should be send through SSL channel.
  • Authentication Required: If the option is enabled then login and password will be required for authentication.
  • Login: User name only required if 'Authentication' is enabled.
  • Password: Password is required only if 'Authentication' is enabled.
  • To: Specify email recipients (more then one recipient can be specified in this area).
  • Select the events for which the notification is required, listed on the tab.
  • After configuring you have to Apply Configurations as well. See how to apply.
 
 
    See Also
 
Copyright © 2005-2012 Alachisoft. All rights reserved.