[jira] [Commented] (HDFS-333) A State Machine for name-node blocks.
[ https://issues.apache.org/jira/browse/HDFS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14068760#comment-14068760 ] Allen Wittenauer commented on HDFS-333: --- Given the changes with HA, etc, I wonder if this is still valid. Ping! A State Machine for name-node blocks. - Key: HDFS-333 URL: https://issues.apache.org/jira/browse/HDFS-333 Project: Hadoop HDFS Issue Type: Improvement Reporter: Konstantin Shvachko Blocks on the name-node can belong to different collections like the blocksMap, under-replicated, over-replicated lists, etc. It is getting more and more complicated to keep the lists consistent. It would be good to formalize the movement of the blocks between the collections using a state machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HDFS-333) A State Machine for name-node blocks.
[ https://issues.apache.org/jira/browse/HDFS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14069249#comment-14069249 ] Konstantin Shvachko commented on HDFS-333: -- It is still valid. It would formalize and simplify block life cycle management. A State Machine for name-node blocks. - Key: HDFS-333 URL: https://issues.apache.org/jira/browse/HDFS-333 Project: Hadoop HDFS Issue Type: Improvement Reporter: Konstantin Shvachko Blocks on the name-node can belong to different collections like the blocksMap, under-replicated, over-replicated lists, etc. It is getting more and more complicated to keep the lists consistent. It would be good to formalize the movement of the blocks between the collections using a state machine. -- This message was sent by Atlassian JIRA (v6.2#6252)
