[infinispan-issues] [JBoss JIRA] (ISPN-3704) StateTransfer's PutKeyValueCommand may trigger remote get

Radim Vansa (JIRA) jira-events at lists.jboss.org
Wed Nov 13 12:14:05 EST 2013


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

Radim Vansa commented on ISPN-3704:
-----------------------------------

Increasing priority as the remote get timeout is pretty long and if the ST transaction gets aborted (due to timeout), we lose that entry.
                
> StateTransfer's PutKeyValueCommand may trigger remote get
> ---------------------------------------------------------
>
>                 Key: ISPN-3704
>                 URL: https://issues.jboss.org/browse/ISPN-3704
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 6.0.0.CR1
>            Reporter: Radim Vansa
>            Assignee: Mircea Markus
>            Priority: Critical
>
> In TX mode with write skew check on, ST executing puts may trigger a remote get.
> The condition in TxDistributionInterceptor.handleTxWriteCommand should probably be switched from
> {code}
> if (ctx.isOriginLocal() && !skipRemoteGet || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command))
>      remoteGetBeforeWrite(ctx, command, recipientGenerator);
> {code}
> to 
> {code}
> if (!skipRemoteGet && (ctx.isOriginLocal() || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command)))
>      remoteGetBeforeWrite(ctx, command, recipientGenerator);
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the infinispan-issues mailing list