[
https://issues.jboss.org/browse/ISPN-1216?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-1216:
-----------------------------------
It'd be a nice addition but this is not urgent, so postpone it.
It needs further investigation to figure out which of the two timeouts the EOFException is
coming from, whether:
{code}distributedSync.acquireProcessingLock(true,
configuration.getStateRetrievalTimeout(), MILLISECONDS);{code}
Or the flush:
{code}distributedSync.blockUntilAcquired(flushTimeout, MILLISECONDS);{code}
Separate delimiter processing lock timeouts in state transfer
-------------------------------------------------------------
Key: ISPN-1216
URL:
https://issues.jboss.org/browse/ISPN-1216
Project: Infinispan
Issue Type: Enhancement
Components: State transfer
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.1.0.BETA1
It appears that majority of EOFException instances encountered during state transfer are
due to lock acquisition problem in the processing lock.
So, consider adding a different limiter when the processing lock timeout is encountered.
This should allow the receiving end to know more about the exact problem encountered by
the sender side and so could provide more hints to the user.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira