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 2007/03/06 19:07:24 UTC

[jira] Commented: (HADOOP-1065) DFS client warnings / info's should be centrally logged by name node

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

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

The namenode currently exposes a RPC called reportBadBlock() that allows a client to report blocks that have bad crc. The namenode silently deletes those bad blocks. Oops!

In the current implementation, the client does not report failed read/write retry attempts to the namenode. It should.



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