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

Raghu Angadi commented on HADOOP-1603:
--------------------------------------

hmm.. I think we should remove this perticular test. This tests how many 
datanodes reported the block, which is unrelated to what checkpoint does. 
Mostly in your case, this check was done before the third datanode reported its 
blocks. If you  still have it, could you attach build/test/TEST*Checkpoint.txt?


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

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

Reply via email to