[
https://issues.apache.org/jira/browse/HBASE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614291#action_12614291
]
LN commented on HBASE-745:
--------------------------
> With respect to MapFile extensions in HBase, see HStoreFile$HBaseMapFile,
> HStoreFile$BloomFilterMapFile > and HStoreFile$HalfMapFileReader
i have noticed the inheritance between HStoreFile$xxxMapFile classes, since all
xxxReader inherited from HStoreFile$HbaseMapFile$HbaseReader, it is a good
point for us controlling all reading operations in HbaseReader, so my
suggestion is let HbaseReader extends a new class(extends MapFile.Reader), we
do limitations in there.
> scaling of one regionserver, improving memory and cpu usage
> -----------------------------------------------------------
>
> Key: HBASE-745
> URL: https://issues.apache.org/jira/browse/HBASE-745
> Project: Hadoop HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.1.3, 0.2.0
> Environment: hadoop 0.17.1
> Reporter: LN
> Priority: Minor
> Attachments: HBASE-745.compact.patch
>
>
> after weeks testing hbase 0.1.3 and hadoop(0.16.4, 0.17.1), i found there are
> many works to do, before a particular regionserver can handle data about
> 100G, or even more. i'd share my opions here with stack, and other developers.
> first, the easiest way improving scalability of regionserver is upgrading
> hardware, use 64bit os and 8G memory for the regionserver process, and speed
> up disk io.
> besides hardware, following are software bottlenecks i found in regionserver:
> 1. as data increasing, compaction was eating cpu(with io) times, the total
> compaction time is basicly linear relative to whole data size, even worse,
> sometimes square relavtive to that size.
> 2. memory usage are depends on opened mapfiles
> 3. network connection are depends on opened mapfiles, see HADOOP-2341 and
> HBASE-24.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
