-
1. Re: Concurrent read writes to root node of treecache in a cluster
galder.zamarreno Jan 18, 2012 7:29 AM (in response to sandkuma)Hmmm, what kind of data consistency issues exactly? Can you post a test case that we can run to replicate this issue?
getKeys(), when the cache is distributed, will result in a local lookup of the node (if L1 is enabled) and if not present, it'll try to load the node from the cluster.
-
2. Re: Concurrent read writes to root node of treecache in a cluster
sandkuma Jan 18, 2012 10:55 AM (in response to galder.zamarreno)We do not have l1 enabled but we find that getkeys returns only local keys. We do not have configuraition file we are starting caches dynamically using startCaches api. Also we are using the tree cache.
The data consistency issue happened because we try to get all the keys using getKeys or getAllChildren of treecache api expecting it to return clusterwide results. Since that results in local keys/children our code has data inconsistencies.
-
3. Re: Concurrent read writes to root node of treecache in a cluster
galder.zamarreno Jan 19, 2012 5:40 AM (in response to sandkuma)Hmmm, that sounds weird. Could you repeat the test and attach a log with TRACE enabled on org.infinispan package?