Minimum configuration for localstorage=false nodes

Question

We have a grid that provides data for multiple clients. Considering that the client is started with localstorage=false, and all requests are passed to the data nodes, what is the minimum cache-configuration that is required by the clients to participate in the cluster.
Edited by: tfanshteyn on Jul 31, 2009 6:54 AM

Answer 1

It is alright to have the following scheme defined in storage-enabled member:
<distributed-scheme>
<scheme-name>app-scheme-1</scheme-name>
<service-name>DistributedScheme1</service-name>
<backup-count>1</backup-count>
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<local-scheme>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<scheme-name>jdbc</scheme-name>
<class-scheme>
<class-name>misc.MyCacheStore</class-name>
</class-scheme>
</cachestore-scheme>
<write-delay-seconds>{delay 5}</write-delay-seconds>
</read-write-backing-map-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>
and client (storage-disabled) with:
<distributed-scheme>
<scheme-name>app-scheme-1</scheme-name>
<service-name>DistributedScheme1</service-name>
<autostart>true</autostart>
</distributed-scheme>
But as Aleks has mentioned in the previous reply it is much easier to manage and distribute single cache configuration even though there a quite a few configs that can be different. Any "data" specific settings like CacheStore will only trigger where that Entry is, so on a localstorage=false nodes these settings are not required. But keep in mind as the applications grow managing multiple cache configurations can become quite problematic.