[ https://issues.apache.org/jira/browse/HDFS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771207#action_12771207 ]
Konstantin Shvachko commented on HDFS-611: ------------------------------------------ # Do we still need to send a partial list of blocks from the name-node in the BlockCommand? This was the reason we did it in the first place, right? So may be now we can send all blocks at once while data-node controls how fast it removes them. # I'd suggest something with Replica instead of Block, like ReplicaFileDeleter. Data-nodes store *replicas* of *blocks* known to the name-node. # There are 27 unnecessary imports in the new file, it would be good to clean this up. > Heartbeats times from Datanodes increase when there are plenty of blocks to > delete > ---------------------------------------------------------------------------------- > > Key: HDFS-611 > URL: https://issues.apache.org/jira/browse/HDFS-611 > Project: Hadoop HDFS > Issue Type: Bug > Components: data-node > Affects Versions: 0.20.1, 0.21.0, 0.22.0 > Reporter: dhruba borthakur > Assignee: Zheng Shao > Fix For: 0.20.2, 0.21.0, 0.22.0 > > Attachments: HDFS-611.branch-19.patch, HDFS-611.branch-20.patch, > HDFS-611.trunk.patch > > > I am seeing that when we delete a large directory that has plenty of blocks, > the heartbeat times from datanodes increase significantly from the normal > value of 3 seconds to as large as 50 seconds or so. The heartbeat thread in > the Datanode deletes a bunch of blocks sequentially, this causes the > heartbeat times to increase. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.