[jira] [Updated] (HDFS-7211) Block invalidation work should be ordered

2017-01-06 Thread Junping Du (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junping Du updated HDFS-7211:
-
Target Version/s:   (was: 2.8.0)

> Block invalidation work should be ordered
> -
>
> Key: HDFS-7211
> URL: https://issues.apache.org/jira/browse/HDFS-7211
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: namenode
>Affects Versions: 2.5.1
>Reporter: Zhe Zhang
>Assignee: Zhe Zhang
>
> {{InvalidateBlocks#node2blocks}} uses an unordered {{LightWeightHashSet}} to 
> store blocks (to be invalidated) on the same DN. This causes poor ordering 
> when a single DN has a large number of blocks to invalidate. Blocks should be 
> invalidated following the order of invalidation commands -- at least roughly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-7211) Block invalidation work should be ordered

2014-10-20 Thread Andrew Wang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HDFS-7211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Wang updated HDFS-7211:
--
  Component/s: namenode
 Target Version/s: 2.7.0
Affects Version/s: 2.5.1

 Block invalidation work should be ordered
 -

 Key: HDFS-7211
 URL: https://issues.apache.org/jira/browse/HDFS-7211
 Project: Hadoop HDFS
  Issue Type: Bug
  Components: namenode
Affects Versions: 2.5.1
Reporter: Zhe Zhang
Assignee: Zhe Zhang

 {{InvalidateBlocks#node2blocks}} uses an unordered {{LightWeightHashSet}} to 
 store blocks (to be invalidated) on the same DN. This causes poor ordering 
 when a single DN has a large number of blocks to invalidate. Blocks should be 
 invalidated following the order of invalidation commands -- at least roughly. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)