[
https://issues.jboss.org/browse/ISPN-1610?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1610:
-----------------------------------------------
Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug
765759|https://bugzilla.redhat.com/show_bug.cgi?id=765759]
Yesterday I had a chat with dberindei on this. The problem here is that this is not an
exception that occurs due to exceeded timeout while waiting on state transfer lock. In our
tests we have the timeout set to 10 minutes and e.g. in the resilience test no state
transfer took more than 10 sec.
This happens when the lock is denied immediately as a result of state transfer being
started with different delays on different nodes (as explained in ISPN-1610) to prevent
deadlock:
https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o...
The situation that causes this exception to appear is quite normal and expected, but the
exception and the error message by which it is reported is not a suitable one.
Timeouts waiting for StateTransferLock
--------------------------------------
Key: ISPN-1610
URL:
https://issues.jboss.org/browse/ISPN-1610
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.1.0.CR1
Reporter: Tristan Tarrant
Assignee: Dan Berindei
Priority: Minor
In a four node performance tests we're seeing these exceptions during cluster
startup:
org.infinispan.distribution.StateTransferInProgressException: Timed out waiting for the
state transfer lock, state transfer in progress for view X
The timeout is set to the default 1min. It's quite suspicious that a state transfer
takes that long ( > 1min) since caches are empty.
--
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