[
https://issues.apache.org/jira/browse/HDFS-8795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Liu updated HDFS-8795:
-------------------------
Description:
Currently we use {{TreeMap}} for {{node2blocks}}, actually there are only two
place may need sorted: {{dump}}, {{getDatanodes}}. But {{getDatanodes}} is
called by {{computeInvalidateWork}}, and we do a shuffle there, so the sort is
unnecssary. For {{dump}}, certainly we need to make few modification.
So we can use {{HashMap}}.
>From memory and performance view, {{HashMap}} is better than {{TreeMap}}, a
>simliar optimization HDFS-7433.
was:
Currently we use {{TreeMap}} for {{node2blocks}}, actually there are only two
place may need sorted: {{dump}}, {{getDatanodes}}. But {{getDatanodes}} is
called by {{computeInvalidateWork}}, and we do a shuffle there, so the sort is
unnecssary. For {{dump}}, certainly we can modify few log.
So we can use {{HashMap}}.
>From memory and performance view, {{HashMap}} is better than {{TreeMap}}, a
>simliar optimization HDFS-7433.
> Improve InvalidateBlocks
> ------------------------
>
> Key: HDFS-8795
> URL: https://issues.apache.org/jira/browse/HDFS-8795
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Yi Liu
> Assignee: Yi Liu
>
> Currently we use {{TreeMap}} for {{node2blocks}}, actually there are only two
> place may need sorted: {{dump}}, {{getDatanodes}}. But {{getDatanodes}} is
> called by {{computeInvalidateWork}}, and we do a shuffle there, so the sort
> is unnecssary. For {{dump}}, certainly we need to make few modification.
> So we can use {{HashMap}}.
> From memory and performance view, {{HashMap}} is better than {{TreeMap}}, a
> simliar optimization HDFS-7433.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
