[
https://issues.apache.org/jira/browse/HBASE-16556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15462028#comment-15462028
]
Hudson commented on HBASE-16556:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #1536 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/1536/])
HBASE-16556 The read/write timeout are not used in HTable.delete(List), (tedyu:
rev 592245ff1307f72161aa64774aa891248bb968de)
* (edit)
hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestAsyncProcess.java
* (edit)
hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/RegionCoprocessorEnvironment.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> 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.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)
