You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/09/04 21:40:20 UTC

[jira] [Reopened] (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:all-tabpanel ]

Ted Yu reopened HBASE-16556:
----------------------------

> 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
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16556.branch-1.v0.patch, 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)