You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Todd Lipcon (Created) (JIRA)" <ji...@apache.org> on 2011/11/02 04:16:32 UTC
[jira] [Created] (HDFS-2529) lastDeletedReport should be scoped to
BPOfferService, not DN
lastDeletedReport should be scoped to BPOfferService, not DN
------------------------------------------------------------
Key: HDFS-2529
URL: https://issues.apache.org/jira/browse/HDFS-2529
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.23.0
Reporter: Todd Lipcon
Each BPOfferService separately tracks and reports deleted blocks. But, lastDeletedReport is a member variable in DataNode, so deletion reports may not be triggered on the desired interval.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HDFS-2529) lastDeletedReport should be scoped to
BPOfferService, not DN
Posted by "Uma Maheswara Rao G (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-2529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Uma Maheswara Rao G resolved HDFS-2529.
---------------------------------------
Resolution: Duplicate
Release Note: Since this is covered as part of HDFS-2560, duplicated with it.
> lastDeletedReport should be scoped to BPOfferService, not DN
> ------------------------------------------------------------
>
> Key: HDFS-2529
> URL: https://issues.apache.org/jira/browse/HDFS-2529
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
>
> Each BPOfferService separately tracks and reports deleted blocks. But, lastDeletedReport is a member variable in DataNode, so deletion reports may not be triggered on the desired interval.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira