[
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571069#comment-13571069
]
Anoop Sam John commented on HBASE-3787:
---------------------------------------
Another option would be to make the 2nd attempt a success and just return the
Result, without doing the operation.
Also wrt OperationInProgress, we can throw the Exception but what the client
need to do.(HBase client not the app). Still it is not sure abt the status of
the operation , whether it will be success or failure.
The whole point here coming is how to query, from client, the result of an old
operation happened in server.
> 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
