[infinispan-issues] [JBoss JIRA] (ISPN-1602) Single view change causes stale locks

[ https://issues.jboss.org/browse/ISPN-1602?page=com.atlassian.jira.plugin.... ] Erik Salter edited comment on ISPN-1602 at 12/19/11 6:04 PM: ------------------------------------------------------------- Now there are lock timeouts with a stable cluster (no rehash) with ISPN-1584 applied. http://dl.dropbox.com/u/50401510/5.1.0.CR2/200threads-withoutrehash.7z (I apologize in advance for the size of this file.) A good place to start is ServiceGroupKey[edgeDeviceId=45,serviceGroupNo=144] on dht14. This test is with 200 threads accessing 252 keys. The only thing interesting about this cache is that it's simply an aggregator. No data is being stored in this cache. For reference, there is another cache (SopSegment) that has these 200 threads accessing 4 keys without issue. EDIT: Here is the issue reproduced with a bit more sane log size and only one cluster in test. All the locks become stale once two nodes drop out of the cluster. http://dl.dropbox.com/u/50401510/5.1.0.CR2/stalelock.tgz. was (Author: an1310): Now there are lock timeouts with a stable cluster (no rehash) with ISPN-1584 applied. http://dl.dropbox.com/u/50401510/5.1.0.CR2/200threads-withoutrehash.7z (I apologize in advance for the size of this file.) A good place to start is ServiceGroupKey[edgeDeviceId=45,serviceGroupNo=144] on dht14. This test is with 200 threads accessing 252 keys. The only thing interesting about this cache is that it's simply an aggregator. No data is being stored in this cache. For reference, there is another cache (SopSegment) that has these 200 threads accessing 4 keys without issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira