[infinispan-issues] [JBoss JIRA] (ISPN-1799) We should avoid using exceptions for flow control when acquiring state transfer lock

[dex chen (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12686273#comment-12686273 ] 

dex chen commented on ISPN-1799:
--------------------------------

we saw this error in our 3 node cluster in which the network connectivity to one of nodes is not reliable and has high latency.  Does this exception have anything to do with the network connectivity and high latency?
                
> We should avoid using exceptions for flow control when acquiring state transfer lock
> ------------------------------------------------------------------------------------
>
>                 Key: ISPN-1799
>                 URL: https://issues.jboss.org/browse/ISPN-1799
>             Project: Infinispan
>          Issue Type: Task
>          Components: State transfer
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 5.2.0.FINAL
>
>
> We currently use `StateTransferInProgressException` as a marker that a write command failed to acquire the state transfer lock and it should be retried. With ISPN-1704 I added another exception, StateTransferLockReacquisitionException, to signal that a write command failed to re-acquire the state transfer lock after it had already acquired it.
> These exceptions often appear in the logs and confuse users (see ISPN-1610), so it would be best to use special return values. We may also need a flag in the InvocationContext for StateTransferLockReacquisitionException.

--
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