You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2008/03/17 07:29:24 UTC

[jira] Updated: (HADOOP-3029) Misleading log message "firstbadlink" printed by datanodes

     [ https://issues.apache.org/jira/browse/HADOOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HADOOP-3029:
-------------------------------------

    Attachment: firstbadlink.patch

Print the firstbadlink error message only if log level is set to DEBUG or there is actually an error.

> Misleading log message "firstbadlink" printed by datanodes
> ----------------------------------------------------------
>
>                 Key: HADOOP-3029
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3029
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: firstbadlink.patch
>
>
> HADOOP-1707 introduces a  DataNode log message of the form "forwarding connect ack to upstream firstbadlink is". This log message does not really mean that any bad links were found. This log message should be changed so that it does not get printed in INFO level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.