How Server Settings Can Override Client Settings

Edit online

The tc.property, ehcache.clustered.config.override.mode, allows you to determine if and how the cache settings on the server override the cache settings on the client. You can set this tc.property in the tc-config.xml file or define it as a system property with the com.tc. prefix.

The possible values are:

  • NONE- Default behavior: any discrepancy between the client and server versions of a cache configuration option causes the client to throw an exception.
  • GLOBAL- Allows any cache-wide settings from the server to override those from the client. For example, if a client were to join with a TTI=10 while the server has a TTI=15, then
    • The server TTI value overrides the client TTI value.
    • Local settings, such as maxEntriesLocalHeap, are not overridden.
  • ALL - Causes the client to accept all values from the server’s configuration. This includes the cache-wide settings of GLOBAL as well as the local settings, such as maxBytesLocalHeap.