[
https://issues.apache.org/jira/browse/HADOOP-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512651
]
Bryan Pendleton commented on HADOOP-1603:
-----------------------------------------
Seeing this on a cluster running a checkout of release-0.13.0. Haven't lost any
blocks yet, but had some close calls....
Not sure where to mention it, but it exposes a limitation of the "when down
replication happens, clear blocks from the fullest node first" working against
the "try to distribute replications across racks".
> 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
> Assignee: 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.
