hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jitendra Nath Pandey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5780) Fix slightly confusing log from "-metaSave" on NameNode
Date Thu, 27 Aug 2009 00:20:59 GMT

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

Jitendra Nath Pandey updated HADOOP-5780:
-----------------------------------------

    Attachment: HADOOP-5780.hadoop-0.20.patch

Patch for hadoop-0.20

> Fix slightly confusing log from "-metaSave" on NameNode
> -------------------------------------------------------
>
>                 Key: HADOOP-5780
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5780
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.20.0
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-5780.hadoop-0.20.patch, HADOOP-5780.patch, HADOOP-5780.patch,
HADOOP-5780.patch
>
>
> After HADOOP-4103, "-metaSave" on NameNode prints "MISSING" in the line for a block that
does not have any good replicas left. 
> e.g. : {noformat}
> Metasave: Blocks waiting for replication: 1
> blk_6735500019364591152_0 (replicas: l: 0 d: 0 c: 2 e: 0 MISSING) 74.6.132.200:50010
:  192.168.0.107:50010 :
> {noformat}
> "0 MISSING" in the log might imply to the user that there is no missing block, though
it implies "e(xcess replicas) : 0".
> We should fix that. Also as part of this I would like to indicate which datanodes are
decommissioned or contain the corrupt replicas.

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