Operation Timeout
Operation Timeout in NCache is a very important cluster-level configuration that specifies the time, in seconds, allotted for a clustered operation to be completed before it fails/terminates because of a timeout. It's a failsafe mechanism that prevents a clustered operation from using cluster resources when it hangs, thus ensuring a very high level of availability in a distributed environment.
Even though the default time limit for Operation Timeout in NCache is 60 seconds, it can be configured to work with high-latency networks or when handling a large amount of data by adjusting this time limit according to system requirements. The Operation Timeout can be changed in the following ways:
Configure Operation Timeout via the NCache Management Center
Launch the NCache Management Center by browsing to http://localhost:8251 or
<server-ip>:8251.In the left navigation bar, click on Clustered Caches or Local Caches, based on the cache to configure.
Against the Cache Name, click on View Details.

This opens up the detailed configuration page for the cache. Go to the Advanced Settings tab and click on Cluster Settings in the left bar.
Change the Operation timeout present in the Advanced Cluster Options section.

- Click on Save Changes present at the bottom of the page to apply this configuration to the cache.
Manually Configure Operation Timeout in config.ncconf
You can manually edit the NCache configuration as explained below:
Important
Ensure the cache stops before making any configuration changes.
- Specify operation timeout through config.ncconf by specifying the
operation-timeoutin the<cluster-settings>tag:
<cache-topology topology="partitioned-replica">
<cluster-setting operation-timeout="60sec" stats-repl-interval="60sec" use-heart-beat="False">
...
</cluster-setting>
</cache-topology>
- Once changes are made, start the cache, and restart the NCache Service.
See Also
Ports
Statistic Replication Interval
Connection Retries
Retry Interval