hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1603) Replication gets set to 1 sometimes when Namenode restarted.
Date Mon, 16 Jul 2007 18:16:04 GMT

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

Raghu Angadi commented on HADOOP-1603:

I am preparing a patch. All constructors of FSNamesystem will take configuration and common
initialization will be moved to a separate private member.

> Replication gets set to 1 sometimes when Namenode restarted.
> ------------------------------------------------------------
>                 Key: HADOOP-1603
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1603
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.13.0
>            Reporter: Raghu Angadi
>            Assignee: Raghu Angadi
>            Priority: Blocker
>             Fix For: 0.13.0
> I have seen this with at least 3-4 weeks old trunk. It is not very deterministic but
when the cluster restarts all files get their replication reset to 1. It is not deterministic
but not very hard  to reproduce. I could reproduce this on a small cluster. I will add more

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message