[
https://issues.apache.org/jira/browse/HBASE-10337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892661#comment-13892661
]
Hudson commented on HBASE-10337:
--------------------------------
FAILURE: Integrated in HBase-TRUNK #4889 (See
[https://builds.apache.org/job/HBase-TRUNK/4889/])
Amend HBASE-10337 HTable.get() uninteruptible; add missing license headers
(apurtell: rev 1564861)
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/ExceptionUtil.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestClientOperationInterrupt.java
HBASE-10337 HTable.get() uninteruptible (Nicolas Liochon) (apurtell: rev
1564851)
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/client/RpcRetryingCaller.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClient.java
*
/hbase/trunk/hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java
*
/hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/ExceptionUtil.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestClientOperationInterrupt.java
> HTable.get() uninteruptible
> ---------------------------
>
> Key: HBASE-10337
> URL: https://issues.apache.org/jira/browse/HBASE-10337
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.0, 0.94.9, 0.99.0, 0.96.1.1
> Reporter: Jonathan Leech
> Assignee: Nicolas Liochon
> Fix For: 0.98.0, 0.99.0
>
> Attachments: 10337-addendum.patch, 10337.v1.patch, 10337.v2.patch
>
>
> I've got a stuck thread on HTable.get() that can't be interrupted, looks like
> its designed to be interruptible but can't be in interrupted in practice due
> to while loop.
> The offending code is in org.apache.hadoop.hbase.ipc.HBaseClient.call() line
> 981, it catches InterruptedException then goes right back to waiting due to
> the while loop.
> It looks like future versions of the client (.95+) are significantly
> different and might not have this problem... Not sure about release schedules
> etc. or if this version is still getting patched.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
