[
https://issues.apache.org/jira/browse/HBASE-3787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13816873#comment-13816873
]
Sergey Shelukhin commented on HBASE-3787:
-----------------------------------------
[~ndimiduk] asked me... some review guideline (of course you can review in any
order).
1) Client nonce generator, as well as additions to testMultiParallel and test
log replay to get the idea of the feature.
2) Test of the nonce manager and nonce manager to see server nonce handling and
how it works.
3) Plumbing (most of the patch), unfortunately there isn't any good order to
review plumbing... perhaps:
a) protobuf and client changes.
b) server and log replay changes.
> 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
> Assignee: Sergey Shelukhin
> Priority: Blocker
> Attachments: HBASE-3787-partial.patch, HBASE-3787-v0.patch,
> HBASE-3787-v1.patch, HBASE-3787-v2.patch, HBASE-3787-v3.patch,
> HBASE-3787-v4.patch, HBASE-3787-v5.patch, HBASE-3787-v5.patch,
> HBASE-3787-v6.patch, HBASE-3787-v7.patch, HBASE-3787-v8.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
