You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2012/05/20 06:50:46 UTC

[jira] [Comment Edited] (HBASE-5699) Run with > 1 WAL in HRegionServer

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

Lars Hofhansl edited comment on HBASE-5699 at 5/20/12 4:49 AM:
---------------------------------------------------------------

I suspect this will become more important when people eventually turn on HBASE-5954 (durable sync, if they don't run in data centers with backup power supplies).

bq. There would be many regions in a cluster. They may not receive even write load.

Is that necessarily a problem? Just saying that while we are exploring this, might as well explore this option as well. I for one be happy if a region's edits are tied to that region and log splitting could just go away (well almost, would still need to split if the region is split).

                
      was (Author: lhofhansl):
    I suspect this will become more important when people eventually turn on HBASE-5954 (durable sync, if they don't in data centers with backup power supplies).

bq. There would be many regions in a cluster. They may not receive even write load.

Is that necessarily a problem? Just saying that while we are exploring this, might as well explore this option as well. I for one be happy if a region's edits are tied to that region and log splitting could just go away (well almost, would still need to split if the region is split).

                  
> Run with > 1 WAL in HRegionServer
> ---------------------------------
>
>                 Key: HBASE-5699
>                 URL: https://issues.apache.org/jira/browse/HBASE-5699
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: binlijin
>            Assignee: Li Pi
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira