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] Updated: (HADOOP-1603) Replication gets set to 1 sometimes when Namenode restarted.
Date Tue, 17 Jul 2007 20:16:04 GMT

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

Raghu Angadi updated HADOOP-1603:

    Attachment: HADOOP-1603-branch13-02.patch

Thanks Konstantin. 

# changed the new member name to setConfigurationParameters()
# patch for trunk uses getFileStatus() for replication. Yesterday I made the TestCheckpoint.java
patch for 13 then applied it to trunk, otherwise I wouldn't have missed eclipse's loud screams
about the use of deprecated functions.

> 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
>         Attachments: HADOOP-1603-branch13-02.patch, HADOOP-1603-branch13-02.patch, HADOOP-1603-branch13-02.patch,
HADOOP-1603-trunk-02.patch, HADOOP-1603-trunk-02.patch, HADOOP-1603-trunk-02.patch
> 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