hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3383) AdminService should use "warn" instead of "info" to log exception when operation fails
Date Sat, 21 Mar 2015 01:29:38 GMT

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

Hadoop QA commented on YARN-3383:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12706096/YARN-3383-032015.patch
  against trunk revision 7f1e2f9.

    {color:red}-1 patch{color}.  Trunk compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/7056//console

This message is automatically generated.

> AdminService should use "warn" instead of "info" to log exception when operation fails
> --------------------------------------------------------------------------------------
>
>                 Key: YARN-3383
>                 URL: https://issues.apache.org/jira/browse/YARN-3383
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Li Lu
>         Attachments: YARN-3383-032015.patch
>
>
> Now it uses info:
> {code}
>   private YarnException logAndWrapException(IOException ioe, String user,
>       String argName, String msg) throws YarnException {
>     LOG.info("Exception " + msg, ioe);
> {code}
> But it should use warn instead.



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

Mime
View raw message