hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kannan Muthukkaruppan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6981) multiple commit logs per region server
Date Fri, 12 Oct 2012 19:23:03 GMT

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

Kannan Muthukkaruppan commented on HBASE-6981:

Ted: You are right. It is pretty much the same. Liyin is planning to take a look at this issue.
> multiple commit logs per region server
> --------------------------------------
>                 Key: HBASE-6981
>                 URL: https://issues.apache.org/jira/browse/HBASE-6981
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Kannan Muthukkaruppan
>            Assignee: Kannan Muthukkaruppan
> For write dominated workloads, the fact that we have only 1 commit log per server  artificially
limits the aggregate throughput to that of one disk (this is especially true if we do true
FS level syncs on each datanode, or even frequent intermittent FS level syncs as data is being
written to each block).
> We could consider allowing a configurable number of commit logs per server (perhaps something
close to or slightly less than the number of disks per server), and we could shard regions
on the server, by maybe just a simple modulo scheme, into those commit logs.
> [A quick way to experiment with the same might be to run multiple region server instances
per server; but might be better operationally to package the feature into a single region

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message