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:15:24 UTC
[jira] Created: (HADOOP-3029) Misleading log message "firstbadlink"
printed by datanodes
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
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.
[jira] Commented: (HADOOP-3029) Misleading log message
"firstbadlink" printed by datanodes
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579377#action_12579377 ]
Hadoop QA commented on HADOOP-3029:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12378020/firstbadlink.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler warnings.
release audit +1. The applied patch does not generate any new release audit warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests -1. The patch failed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1980/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1980/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1980/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1980/console
This message is automatically generated.
> 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.
[jira] Updated: (HADOOP-3029) Misleading log message "firstbadlink"
printed by datanodes
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-3029) Misleading log message "firstbadlink"
printed by datanodes
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur updated HADOOP-3029:
-------------------------------------
Status: Patch Available (was: Open)
> 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.
[jira] Updated: (HADOOP-3029) Misleading log message "firstbadlink"
printed by datanodes
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-3029) Misleading log message
"firstbadlink" printed by datanodes
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580330#action_12580330 ]
Hudson commented on HADOOP-3029:
--------------------------------
Integrated in Hadoop-trunk #433 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/433/])
> 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.
[jira] Commented: (HADOOP-3029) Misleading log message
"firstbadlink" printed by datanodes
Posted by "dhruba borthakur (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580037#action_12580037 ]
dhruba borthakur commented on HADOOP-3029:
------------------------------------------
I would like to incorporate this into 0.16.2.
> 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.