[ https://issues.apache.org/jira/browse/HADOOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512229 ]
Raghu Angadi commented on HADOOP-1603: -------------------------------------- It usually happens with following steps: # Start Cluster # Creates some files (e.g. run a randomWriter job) # Delete some files (e.g. run another randomWrite job, which deletes earlier files) # Stop cluster (sooner the better). # Start cluster again My impression is that deleting the files in 3rd step somehow causes this. > 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.14.0 > Reporter: Raghu Angadi > Priority: Blocker > Fix For: 0.14.0 > > > 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.