[
https://issues.apache.org/jira/browse/HBASE-21385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865306#comment-16865306
]
Reid Chan commented on HBASE-21385:
-----------------------------------
Ping [~zghaobac], It looks like HBASE-22581 is affected by this patch. (Not
have insight about this)
Would you have free cycles to take a look?
> HTable.delete request use rpc call directly instead of AsyncProcess
> -------------------------------------------------------------------
>
> Key: HBASE-21385
> URL: https://issues.apache.org/jira/browse/HBASE-21385
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0, 2.1.0, 2.2.0, 2.0.2
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Priority: Major
> Fix For: 3.0.0, 2.2.0, 2.1.1, 2.0.3
>
> Attachments: HBASE-21385.master.001.patch,
> HBASE-21385.master.002.patch
>
>
> HBASE-16592 unify delete request to use AsyncProcess. But the job is not done
> totally. As we still use rpc call for get, put, append, and increment. We
> only use AsyncProcess for batch requests. And I found one problem in
> HBASE-21365. The rpc call will throw a DoNotRetryException but AsyncProcess
> will wrap it with a new RetriesExhaustedWithDetailsException. It is not
> right. So I thought HTable.delete should use rpc call directly, it is same
> with get, put, append and increment request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
