Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 11 Dec 2014 12:50:13 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12761040.1418298246000.505.1418302213340@Atlassian.JIRA>
In-Reply-To: <JIRA.12761040.1418298246000@Atlassian.JIRA>
References: <JIRA.12761040.1418298246000@Atlassian.JIRA>
 <JIRA.12761040.1418298246026@arcas>
Subject: [jira] [Commented] (HADOOP-11390) Metrics 2 ganglia provider to
 include hostname in unresolved address problems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran commented on HADOOP-11390:
-----------------------------------------

text is coming from java.net; check for unresolved address would have to be replicated in {{AbstractGangliaSink.emitToGangliaHosts}} and include {{SocketAddress#toString()}} in text

> Metrics 2 ganglia provider to include hostname in unresolved address problems
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-11390
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11390
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 2.6.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> When metrics2/ganglia gets an unresolved hostname it doesn't include the hostname in question, making it harder to track down


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