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] Commented: (HADOOP-1065) DFS client warnings / info's should be centrally logged by name node
Date Wed, 07 Mar 2007 18:11:24 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478833
] 

dhruba borthakur commented on HADOOP-1065:
------------------------------------------

The reportBadBlock was introduced as part of the 855. The Namenode deletes the blocks that
are reported to be bad. It does log it as part of "deletion". My comment was regarding that
fact that maybe we can  enhance the logging to explicitly state "blocks being deleted because
they are bad". Otherwise, from the Namenode log it might be difficult to distinguish blocks
that are deleted because of other reasons (decrease of replication factor, file getting deleted,
etc) from the case when blocks get deleted because they are detected to be bad


> DFS client warnings / info's should be centrally logged by name node
> --------------------------------------------------------------------
>
>                 Key: HADOOP-1065
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1065
>             Project: Hadoop
>          Issue Type: Improvement
>            Reporter: eric baldeschwieler
>
> When a client encounters an error condition that it warns / infos the user about, we
should log that centrally, so that we can mine this info later.  For example CRC errors or
block write retries.

-- 
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