[
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626080#comment-13626080
]
Enis Soztutar commented on HBASE-3787:
--------------------------------------
@Anoop,
bq. You mean the client app right?
Yes, the client app.
bq. For this what do you say? Expose APIs? I got your point with the events
queue use case.
The client will be able to pass a custom nonce to the Mutate object.
bq. so the server should respond something to the effect of "the operation
succeeded, but I don't know what the result is"
I don't think we should bubble up this specific case to the client app unless
we have a valid use case. As long as we document the semantics, it should be
good.
> 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.94.4, 0.95.2
> Reporter: dhruba borthakur
> Priority: Critical
> Fix For: 0.95.1
>
>
> 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
