[
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
Submitting updated patches with the test for block replication removed. In the
test log that Doug attached time between Namenode start and last datanode
registration is around 500 millisec, which makes it more probably for client to
check for for this between datanode registration and block report (client
sleeps for 500 millisec between each check).
> 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.1, 0.14.0
>
> Attachments: HADOOP-1603-branch13-02.patch,
> 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,
> HADOOP-1603-trunk-02.patch, TEST-org.apache.hadoop.dfs.TestCheckpoint.txt
>
>
> 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.
