[
https://issues.jboss.org/browse/ISPN-1610?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-1610:
-------------------------------
Priority: Minor (was: Major)
The state transfer doesn't start at the same time on all the nodes, so sometimes a
command can start on one node and fail with StateTransferInProgressException on the key
owners because state transfer has already started on those nodes. It's not a problem,
as the command is retried after the state transfer starts (and ends) on the command
originator, but it does pollute the logs on the key owners a bit.
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