[ https://issues.apache.org/jira/browse/HADOOP-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291249#comment-14291249 ]
Hadoop QA commented on HADOOP-6221: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12694440/HADOOP-6221-007.patch against trunk revision 35f6496. {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:red}-1 javac{color}. The applied patch generated 1206 javac compiler warnings (more than the trunk's current 1204 warnings). {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-common-project/hadoop-common. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5475//testReport/ Javac warnings: https://builds.apache.org/job/PreCommit-HADOOP-Build/5475//artifact/patchprocess/diffJavacWarnings.txt Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5475//console This message is automatically generated. > RPC Client operations cannot be interrupted > ------------------------------------------- > > Key: HADOOP-6221 > URL: https://issues.apache.org/jira/browse/HADOOP-6221 > Project: Hadoop Common > Issue Type: Bug > Components: ipc > Affects Versions: 0.21.0 > Reporter: Steve Loughran > Assignee: Steve Loughran > Priority: Minor > Attachments: HADOOP-6221-007.patch, HADOOP-6221.patch, > HADOOP-6221.patch, HADOOP-6221.patch, HADOOP-6221.patch, HADOOP-6221.patch, > HADOOP-6221.patch > > > RPC.waitForProxy swallows any attempts to interrupt it while waiting for a > proxy; this makes it hard to shutdown a service that you are starting; you > have to wait for the timeouts. > There are only 4-5 places in the code that use either of the two overloaded > methods, removing the catch and changing the signature should not be too > painful, unless anyone is using the method outside the hadoop codebase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)