[
https://issues.apache.org/jira/browse/HDFS-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13776380#comment-13776380
]
Junping Du commented on HDFS-5222:
----------------------------------
Nicholas, Thanks for your reminder. I didn't think too much on "roll" before as
I was thinking to move count from currApproxBlocksScheduled to (and plus)
prevApproxBlocksScheduled is also a "roll". However, I get some hints from
"Approx" which means not precisely as caused by error cases to make these
values slightly inconsistency. Is that the reason why we periodically cleanup
prevApproxBlocksScheduled (and the main purpose for separating counters to pre
and cur)? If so, that make sense to me.
> Move block schedule information from DatanodeDescriptor to DatanodeStorageInfo
> ------------------------------------------------------------------------------
>
> Key: HDFS-5222
> URL: https://issues.apache.org/jira/browse/HDFS-5222
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: h5222_20130819.patch, h5222_20130824.patch
>
>
> In HDFS-4990, the block placement target type was changed from
> DatanodeDescriptor to DatanodeStorageInfo. The block schedule information,
> such as the number of blocks scheduled for replication (i.e.
> getBlocksScheduled()), should be moved from DatanodeDescriptor to
> DatanodeStorageInfo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
