hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7430) Rewrite the BlockScanner to use O(1) memory and use multiple threads
Date Fri, 13 Feb 2015 23:25:15 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14320962#comment-14320962

Hudson commented on HDFS-7430:

SUCCESS: Integrated in Hadoop-trunk-Commit #7109 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7109/])
update CHANGES.txt for HDFS-7430, HDFS-7721, HDFS-7686 (cmccabe: rev 19be82cd1614000bb26e5684f763c736ea46ff1a)
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

> 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: 2.7.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

View raw message