Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 6 Jul 2015 17:42:04 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12653899.1371721965000.108178.1436204524876@Atlassian.JIRA>
In-Reply-To: <JIRA.12653899.1371721965000@Atlassian.JIRA>
References: <JIRA.12653899.1371721965000@Atlassian.JIRA>
 <JIRA.12653899.1371721965155@arcas>
Subject: [jira] [Commented] (HADOOP-9657) NetUtils.wrapException to have
 special handling for 0.0.0.0 addresses and :0 ports
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-9657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14615364#comment-14615364 ] 

Hadoop QA commented on HADOOP-9657:
-----------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  20m 39s | Pre-patch trunk compilation is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any @author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. |
| {color:green}+1{color} | javac |  11m 26s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |  13m 16s | There were no new javadoc warning messages. |
| {color:green}+1{color} | release audit |   0m 44s | The applied patch does not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   2m 18s | There were no new checkstyle issues. |
| {color:red}-1{color} | whitespace |   0m  0s | The patch has 1  line(s) that end in whitespace. Use git apply --whitespace=fix. |
| {color:green}+1{color} | install |   2m 11s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   1m  0s | The patch built with eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   3m 54s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | common tests |  27m 31s | Tests passed in hadoop-common. |
| | |  83m  3s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12743745/HADOOP-9657.01.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / fc92d3e |
| whitespace | https://builds.apache.org/job/PreCommit-HADOOP-Build/7159/artifact/patchprocess/whitespace.txt |
| hadoop-common test log | https://builds.apache.org/job/PreCommit-HADOOP-Build/7159/artifact/patchprocess/testrun_hadoop-common.txt |
| Test Results | https://builds.apache.org/job/PreCommit-HADOOP-Build/7159/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf904.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/7159/console |


This message was automatically generated.

> NetUtils.wrapException to have special handling for 0.0.0.0 addresses and :0 ports
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-9657
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9657
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: net
>    Affects Versions: 2.7.0
>            Reporter: Steve Loughran
>            Assignee: Varun Saxena
>            Priority: Minor
>         Attachments: HADOOP-9657.01.patch
>
>
> when an exception is wrapped, it may look like {{0.0.0.0:0 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused}}
> We should recognise all zero ip addresses and 0 ports and flag them as "your configuration of the endpoint is wrong", as it is clearly the case


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)