Reload Service Config
The Reload Service Config option allows you to reload the NCache Service configuration on a server node after configuration changes are made. This is useful when you want the NCache Service to re-read its updated service configuration without performing a full service restart.
NCache Service is responsible for managing caches on a server node, listening on the management port, and handling cache management operations. It also works with cache host processes when caches are started and managed on the server. Because of this, service-level configuration changes must be applied carefully. The NCache Service listens on the management port, which is 8250 by default, and the NCache Management Center runs on port 8251 by default.
Reloading the service configuration is different from restarting the NCache Service. A restart stops and starts the service process, while reload only refreshes the service configuration where supported.
When to Use Reload Service Config
Use Reload Service Config when you have updated service-level configuration and want NCache to re-read the updated configuration from the service configuration file.
Common examples may include configuration changes related to:
- Service-level settings.
- Management-related configuration.
- Network binding settings.
- Other settings maintained in the NCache service configuration file.
Important
Reload Service Config should only be used for configuration settings that support reload at runtime. Some configuration changes may still require restarting the NCache Service to take effect.
Reload Service Config vs Restart Service
The following table explains the difference between reloading the service configuration and restarting the NCache Service:
| Action | What it does | When to use |
|---|---|---|
| Reload Service Config | Re-reads the updated service configuration without restarting the service process. | Use when supported service configuration changes need to be applied without a full service restart. |
| Restart Service | Stops and starts the NCache Service. | Use when configuration changes require a full service restart or when the service needs to be refreshed completely. |
NCache Management Center already supports service management actions such as start, stop, and restart for NCache Service on server nodes. Reloading the service configuration should be treated as a lighter operation than restarting the service.
Using NCache Management Center
You can reload the NCache Service configuration from the NCache Management Center following the steps mentioned below:
Launch the NCache Management Center by browsing to
http://localhost:8251or http://:8251. In the left navigation bar, click Clustered Caches or Local Caches, depending on the cache environment where the server node exists.
Select the cache name and click View Details.
Go to the Server Nodes tab.
Select the server node for which you want to reload the service configuration.
Click the ... button against the selected server node.
Click Reload Service Config.
Confirm the action if a confirmation prompt appears.
After the operation completes, verify that the updated configuration has been applied.
Note
If you have multiple server nodes, repeat this process for each node where the service configuration was changed.
Before Reloading Service Config
Before you reload the service configuration, make sure that:
- The updated configuration has been saved correctly.
- The configuration file contains valid XML.
- The updated setting is supported for reload without service restart.
- You are applying the change on the correct server node.
- The selected server node is reachable from the NCache Management Center.
If the configuration file contains invalid values or malformed XML, the service may fail to apply the updated configuration correctly.
After Reloading Service Config
After the reload operation completes, verify that the expected behavior is applied. Depending on the setting changed, you may need to check:
- Whether the selected server node is still reachable.
- Whether the NCache Management Center can communicate with the server node.
- Whether cache management operations are working as expected.
- Whether clients can still connect to the cache, if the change affects client-server communication.
- Whether cluster nodes can still communicate, if the change affects cluster communication.
