[
https://issues.apache.org/jira/browse/HADOOP-10181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14284235#comment-14284235
]
Hadoop QA commented on HADOOP-10181:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12693340/HADOOP-10181.002.patch
against trunk revision c94c0d2.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-common-project/hadoop-common:
org.apache.hadoop.ha.TestZKFailoverController
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5436//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5436//console
This message is automatically generated.
> GangliaContext does not work with multicast ganglia setup
> ---------------------------------------------------------
>
> Key: HADOOP-10181
> URL: https://issues.apache.org/jira/browse/HADOOP-10181
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Andrew Otto
> Assignee: Andrew Johnson
> Priority: Minor
> Labels: ganglia, hadoop, metrics, multicast
> Attachments: HADOOP-10181.001.patch, HADOOP-10181.002.patch
>
>
> The GangliaContext class which is used to send Hadoop metrics to Ganglia uses
> a DatagramSocket to send these metrics. This works fine for Ganglia
> multicast setups that are all on the same VLAN. However, when working with
> multiple VLANs, a packet sent via DatagramSocket to a multicast address will
> end up with a TTL of 1. Multicast TTL indicates the number of network hops
> for which a particular multicast packet is valid. The packets sent by
> GangliaContext do not make it to ganglia aggregrators on the same multicast
> group, but in different VLANs.
> To fix, we'd need a configuration property that specifies that multicast is
> to be used, and another that allows setting of the multicast packet TTL.
> With these set, we could then use MulticastSocket setTimeToLive() instead of
> just plain ol' DatagramSocket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)