[
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567897#comment-13567897
]
Andrew Purtell commented on HBASE-3787:
---------------------------------------
What we really need as a different model for interaction. A bidirectional event
stream between clients and servers. Clients issue requests. Servers (any
server) acknowledges completion. Implies an async client.
In the absence of that we can at least give the client an indication the op has
been processed even through a retry as long as the region doesn't move. (Add to
my OperationInProgressException also OperationAlreadyCompletedException.)
If the region relocates, then we expose some uncertainty to the application by
failing any additional retries. This will be less surprising than current
behavior because we won't have silent application of the same op more than
once, but punts to the app which isn't great either.
> Increment is non-idempotent but client retries RPC
> --------------------------------------------------
>
> Key: HBASE-3787
> URL: https://issues.apache.org/jira/browse/HBASE-3787
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.96.0, 0.94.4
> Reporter: dhruba borthakur
> Priority: Critical
> Fix For: 0.96.0
>
>
> The HTable.increment() operation is non-idempotent. The client retries the
> increment RPC a few times (as specified by configuration) before throwing an
> error to the application. This makes it possible that the same increment call
> be applied twice at the server.
> For increment operations, is it better to use
> HConnectionManager.getRegionServerWithoutRetries()? Another option would be
> to enhance the IPC module to make the RPC server correctly identify if the
> RPC is a retry attempt and handle accordingly.
--
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
