hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1603) Replication gets set to 1 sometimes when Namenode restarted.
Date Tue, 17 Jul 2007 19:38:05 GMT

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

Konstantin Shvachko commented on HADOOP-1603:
---------------------------------------------

FileSystem.getReplication() method is deprecated. Use getFileStatus() instead.
I do not particularly like how you named the new method initializeFromConf().
I'd suggest get or setConfigurationParameters(), but I don't mind any other name as long 
as it doesn't contain abbreviations.


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

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