[
https://issues.apache.org/jira/browse/HADOOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513122
]
Konstantin Shvachko commented on HADOOP-1603:
---------------------------------------------
I cannot apply this patch to current trunk.
Looks like there is a conflict with committed patch HADOOP-1562, which already
introduced a configuration parameter for the FSNamespace constructor.
Also this case should be a part of TestCheckpoint, in which currently we always
check that file replication is 1.
I think TestCheckpoint should also test replication factors of 2 and 3.
> 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-01.patch, HADOOP-1603-trunk-01.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.
