[ https://issues.apache.org/jira/browse/HDFS-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jitendra Nath Pandey updated HDFS-15: ------------------------------------- Attachment: HDFS-15.patch.2 New patch with approach suggested by Raghu. > All replicas of a block end up on only 1 rack > --------------------------------------------- > > Key: HDFS-15 > URL: https://issues.apache.org/jira/browse/HDFS-15 > Project: Hadoop HDFS > Issue Type: Bug > Reporter: Hairong Kuang > Assignee: Jitendra Nath Pandey > Priority: Critical > Attachments: HDFS-15.patch, HDFS-15.patch.2 > > > HDFS replicas placement strategy guarantees that the replicas of a block > exist on at least two racks when its replication factor is greater than one. > But fsck still reports that the replicas of some blocks end up on one rack. > The cause of the problem is that decommission and corruption handling only > check the block's replication factor but not the rack requirement. When an > over-replicated block loses a replica due to decomission, corruption, or > heartbeat lost, namenode does not take any action to guarantee that remaining > replicas are on different racks. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.