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

[ https://issues.jboss.org/browse/ISPN-1602?page=com.atlassian.jira.plugin.... ] Bela Ban commented on ISPN-1602: -------------------------------- Erik, I see address with include a siteId. Can I assume you're using RELAY then ? If you do, the weird thing is that I see more than 2 siteIds, which current RELAY doesn't support, how come I'm seeing siteIds ? If you do a grep "protocols.FD" *.log | grep suspect , you'll see that FD did indeed suspect a few members: - dht12 suspected dht11 multiple times - dht12 suspected dht11 because it didn't receive a heartbeat for 24s - dht11 also suspects dht12... So dht11 and dht12 suspected each other, and those were the only members ever suspected by FD. (Note that FD_SOCK did *not* suspect anyone.) Again, possible causes are: - GC. Are you sure you really only observed GCs under 500ms ? Kind of hard to believe, as GC can take ~ 1s / GB, and you mentioned the other day that you had 6GB of heap... - High traffic can cause a loss of heartbeat - Busy CPU: the CPU is busy processing and this can slow the sending of heartbeat-acks down, too - Thread pools sized too small - Thread pools with a rejection policy of "run": this is dangerous because, *if* the thread which received a message has to process it (and blocks in app code), it will not be able to process other messages ! This brings me back to what I said before: #1 Please use one of the default configurations shipped with JGroups 3.0.1 (e.g. udp-largecluster.xml), and make only minor modifications (e.g. thread pool sizes) ! #2 Increase the timeouts in FD #3 If you use RELAY, then be aware that we haven't tested it yet in the context of Infinispan 5.x and JGroups 3.x ! This task will be started soon, but for now the behavior of rebalancing / state transfer in Infinispan is completely undefined/untested for 5.x/3.x ! -- 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