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-6420) Interrupted Exception in LocalContainerLauncher should be logged in warn/info level
Date Sat, 04 Jul 2015 16:38:07 GMT

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

Hudson commented on MAPREDUCE-6420:
-----------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2192 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2192/])
MAPREDUCE-6420. Interrupted Exception in LocalContainerLauncher should be logged in warn/info
level. Contributed by Chang Li (jlowe: rev 826715622e6937887a4e20b3ce327d7e2fd89009)
* hadoop-mapreduce-project/CHANGES.txt
* hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapred/LocalContainerLauncher.java


> Interrupted Exception in LocalContainerLauncher should be logged in warn/info level
> -----------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6420
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6420
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Chang Li
>            Assignee: Chang Li
>             Fix For: 2.8.0
>
>         Attachments: MAPREDUCE-6420.1.patch
>
>
> Interrupted Exception in LocalContainerLauncher should be logged in warn/info levle instead
of error because it won't fail the job. Otherwise it will cause some confusions during debugging



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

Mime
View raw message