hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3188) Lots of errors in logs when daemon startup fails
Date Thu, 20 Oct 2011 13:24:14 GMT

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

Hudson commented on MAPREDUCE-3188:
-----------------------------------

Integrated in Hadoop-Mapreduce-0.23-Build #57 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/57/])
    Merge -c 1186554 from trunk to branch-0.23 to complete fix for MAPREDUCE-3188.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1186555
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/event/AsyncDispatcher.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/service/AbstractService.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/util/AbstractLivelinessMonitor.java

                
> Lots of errors in logs when daemon startup fails
> ------------------------------------------------
>
>                 Key: MAPREDUCE-3188
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3188
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 0.23.0
>
>         Attachments: mr-3188.txt
>
>
> Since the MR2 daemons are made up of lots of component services, if one of those components
fails to start, it will cause the others to shut down as well, even if they haven't fully
finished starting up. Currently, this causes the error output to have a bunch of NullPointerExceptions,
IllegalStateExceptions, etc, which mask the actual root cause error at the top.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message