hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5763) Warn message about httpshuffle in NM logs
Date Mon, 09 Nov 2015 08:39:11 GMT

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

Hudson commented on MAPREDUCE-5763:
-----------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #1378 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/1378/])
MAPREDUCE-5763. Warn message about httpshuffle in NM logs. Contributed (ozawa: rev 668e897538e317d96784f75b4e1f979c72225db7)
* hadoop-mapreduce-project/CHANGES.txt
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-shuffle/src/main/java/org/apache/hadoop/mapred/ShuffleHandler.java


> Warn message about httpshuffle in NM logs
> -----------------------------------------
>
>                 Key: MAPREDUCE-5763
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5763
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Sandy Ryza
>            Assignee: Akira AJISAKA
>             Fix For: 3.0.0, 2.8.0
>
>         Attachments: MAPREDUCE-5763.00.patch
>
>
> {code}
> 2014-02-20 12:08:45,141 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices:
The Auxilurary Service named 'mapreduce_shuffle' in the configuration is for class class org.apache.hadoop.mapred.ShuffleHandler
which has a name of 'httpshuffle'. Because these are not the same tools trying to send ServiceData
and read Service Meta Data may have issues unless the refer to the name in the config.
> 2014-02-20 12:08:45,142 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices:
Adding auxiliary service httpshuffle, "mapreduce_shuffle"
> {code}
> I'm seeing this in my NodeManager logs,  even though things work fine.  A WARN is being
caused by some sort of mismatch between the name of the service (in terms of org.apache.hadoop.service.Service.getName())
and the name of the auxiliary service.



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

Mime
View raw message