Add Client to Cache
Cache clients are lightweight modules through which cache applications can connect to hosted cache servers. You can add local or remote client nodes to existing clustered cache(s) in NCache.
In order to get more detailed explanation of cache clients, please see the Cache Client section.
Step 1: Add Cache Client to Cache
Using NCache Web Manager
Launch NCache Web Manager by browsing to
<server-ip>:8251(Windows and Linux).
In the left navigation bar, click on Clustered Caches or Local Caches, based on the cache to which the client will be added. Against the cache name, click on View Details.
This opens up the detailed configuration page for the cache. The Client Nodes tab displays a list and status of any existing client nodes of the cache.
Click on the button and specify the client node IP. Click on + to add it to the cache. A success notification will be displayed.
- The newly added node is displayed in the Client Nodes list, with client cache status.
You might get prompted with a dialog box upon these changes, asking whether to reload or overwrite the cache config file. For more detail on maintaining data integrity, refer to this chapter.
Add-ClientNode cmdlet enables the user to add one or more client nodes to existing clustered cache(s).
This command adds a client node 22.214.171.124 to a cache named demoClusteredCache already existing on server node 126.96.36.199.
For more properties of this command you can refer to NCache PowerShell Reference.
Add-ClientNode -CacheName demoClusteredCache -Server 188.8.131.52 -ClientNode 184.108.40.206
If you have more than one IP address on a client machine, enter the IP address on which NCache service is running.
Step 2: Verify Addition of Cache Client
You can quickly run a Stress Test Tool that comes with NCache installation to verify that cache clients can make calls to cache servers. To start this test on the cache you just created, please execute Test-Stress in PowerShell:
Test-Stress -CacheName demoClusteredCache
This command starts making cache calls to the cache servers as Test-Stress simulates transactional load on the specified cache. You can monitor the cache performance using PerfMon counters in .NET and .NET Core for Windows.