Distributed Cache Service

Have more questions? Submit a request

Distributed Cache Service (SVDistCache)

High Availability Synchronization

The Distributed Cache service is designed to share integration and application data across multiple servers. This allows a backup or failover node to maintain state and pick up where the primary node left off, ensuring seamless continuity.

Manufacturer: SureView Systems
Product: SVDistCache
Type: Distributed Cache & Health Monitoring Service

Service Features

  • Data Synchronization: Synchronizes cache entries between cluster nodes to ensure data consistency.
  • Peer Health Monitoring: Real-time tracking of connectivity and health status for all nodes in the cluster.
  • Auto-Recovery: Supports "Startup Pull" to automatically fetch the latest data from peers when the service starts.
  • Health Alarming: Integration with SureView to send automated alerts if a cluster peer becomes unreachable.
  • Flexible Hosting: Runs as a Windows Service and supports port sharing via HTTP.SYS.

Configuration (appsettings.json)

The service is configured via the appsettings.json file. Below are the key sections required for operation:

Section Field Description
Cluster NodeId A unique name for this node (e.g., "node-1").
ClusterKey A shared secret key. Must be identical on all nodes.
Peers A list of URLs for other nodes (e.g., ["http://192.168.1.50:5000/cache"]).
HttpSys UrlPrefixes The URL and port the service listens on (Default: port 5000).
Sync StartupPullEnabled When true, the node pulls data from peers immediately on startup.

HTTPS & SSL Configuration

If you choose to use HTTPS (https://) in your UrlPrefixes, you must manually register an SSL certificate with Windows using the netsh command.

  1. Open a Command Prompt as Administrator.
  2. Run the following command, replacing the bracketed values with your specific details:
netsh http add sslcert ipport=0.0.0.0:5000 certhash=YOUR_CERT_THUMBPRINT appid={YOUR_APP_GUID}
  • ipport: Use "0.0.0.0:" followed by your configured port.
  • certhash: The thumbprint of your installed SSL certificate (remove spaces).
  • appid: Any unique GUID (e.g., "00112233-4455-6677-8899-AABBCCDDEEFF").

SureView Health Notifications

The service can send alarms to SureView if it detects that a peer node has gone offline. To enable this, configure the Notification section in the settings:

  • Identifier: The Device Identifier assigned to your Alarm Decoder.
  • Authorization: The API Key found on the HTTP Alarms tab of the Alarm Setup page.
  • WebhookUrl: The address of your SureView Receiver (e.g., "https://us.sureviewops.com/receiver").

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share

Comments

0 comments

Article is closed for comments.