hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3029) Misleading log message "firstbadlink" printed by datanodes
Date Tue, 18 Mar 2008 19:59:24 GMT

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

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

       Resolution: Fixed
    Fix Version/s: 0.17.0
           Status: Resolved  (was: Patch Available)

I just committed this.

> 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
>             Fix For: 0.17.0
>
>         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.


Mime
View raw message