ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vinshar <vinsharma.t...@gmail.com>
Subject Is CacheConfiguration specified at client node ignored in case if Cache already exists?
Date Sat, 09 Jan 2016 16:32:53 GMT
Hi,

What happens in case where i have a cache which is already exists on one of
the server nodes and i try to configure same cache at client node where
configurations at client node differs from configuration on server node used
to start the cache? 

For an example, Lets say in my server node's cache configuration i mentioned
a near cache configuration where as at client node i did not or vice versa?
or i specified a different cache mode in configuration on client node? Are
there some configurations which are ignored whereas some configuration which
are not? or will there be an exception thrown while getting cache at client
node?

Regards,
Vinay Sharma



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-CacheConfiguration-specified-at-client-node-ignored-in-case-if-Cache-already-exists-tp2461.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message