You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2007/07/12 20:26:04 UTC

[jira] Updated: (HADOOP-1603) Replication gets set to 1 sometimes when Namenode restarted.

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

Raghu Angadi updated HADOOP-1603:
---------------------------------

    Component/s: dfs
    Description: 
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. 




  was:

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. 





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