[
https://issues.apache.org/jira/browse/HDFS-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317213#comment-14317213
]
Chris Nauroth commented on HDFS-7430:
-------------------------------------
I didin't review this patch at all, but how are the rest of you who did review
it feeling about merging to branch-2 at this point? I ask because the
difference between trunk and branch-2 is now creating conflicts for other
patches. (See HDFS-7604 and HDFS-7778.) If the plan is still to merge this to
branch-2, then I'll hold off on those other patches until this one is done
merging.
> Rewrite the BlockScanner to use O(1) memory and use multiple threads
> --------------------------------------------------------------------
>
> Key: HDFS-7430
> URL: https://issues.apache.org/jira/browse/HDFS-7430
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Fix For: 3.0.0
>
> Attachments: HDFS-7430.002.patch, HDFS-7430.003.patch,
> HDFS-7430.004.patch, HDFS-7430.005.patch, HDFS-7430.006.patch,
> HDFS-7430.007.patch, HDFS-7430.008.patch, HDFS-7430.009.patch,
> HDFS-7430.010.patch, HDFS-7430.011.patch, HDFS-7430.012.patch, memory.png
>
>
> We should update the BlockScanner to use a constant amount of memory by
> keeping track of what block was scanned last, rather than by tracking the
> scan status of all blocks in memory. Also, instead of having just one
> thread, we should have a verification thread per hard disk (or other volume),
> scanning at a configurable rate of bytes per second.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
