You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/09/03 15:06:20 UTC
[jira] [Commented] (HBASE-16556) The read/write timeout are not
used in HTable.delete(List), HTable.get(List), and HTable.existsAll(List)
[ https://issues.apache.org/jira/browse/HBASE-16556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15461221#comment-15461221 ]
Ted Yu commented on HBASE-16556:
--------------------------------
lgtm
Pending QA result.
> The read/write timeout are not used in HTable.delete(List), HTable.get(List), and HTable.existsAll(List)
> --------------------------------------------------------------------------------------------------------
>
> Key: HBASE-16556
> URL: https://issues.apache.org/jira/browse/HBASE-16556
> Project: HBase
> Issue Type: Bug
> Reporter: ChiaPing Tsai
> Assignee: ChiaPing Tsai
> Priority: Minor
> Attachments: HBASE-16556.v0.patch
>
>
> [HBASE-15866|https://issues.apache.org/jira/browse/HBASE-15866] splits rpc timeout into read timeout and write timeout.
> The HTable.delete(List), HTable.get(List), and HTable.existsAll(List) call AP#batch() to submit data, but they don’t use the read/write timeout argument. So the AP will use the rpc timeout got from hbase.rpc.timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)