[
https://issues.jboss.org/browse/ISPN-1610?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-1610:
-----------------------------------------------
JBoss JIRA Server <jira-update(a)redhat.com> made a comment on [bug
765759|https://bugzilla.redhat.com/show_bug.cgi?id=765759]
Dan Berindei <dberinde(a)redhat.com> made a comment on jira ISPN-1799
Dex, if you have high latency or high losses then your cluster could split into two or
more partitions, and during the split/merge it's possible to see these
StateTransferInProgressExceptions and you can ignore them.
However, you should try to avoid these cluster changes by increasing your FD timeout, as
saturating the network with the state transfer might lead to yet another split.
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