[jira] [Updated] (HBASE-13643) Follow Google to get more 9's

["Mike Drob (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-13643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Drob updated HBASE-13643:
------------------------------
    Fix Version/s: 3.0.0

> Follow Google to get more 9's
> -----------------------------
>
>                 Key: HBASE-13643
>                 URL: https://issues.apache.org/jira/browse/HBASE-13643
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Elliott Clark
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Ideas taken shamelessly from Google's HBasecon talk (http://hbasecon.com/agenda/):
> On failover all regions are unavailable for reads (and sometime writes) until after all write ahead logs have been recovered. To combat that the last flushed seqid is kept around.
> Google took this one step farther and set some regions (Tablets in BigTable) as read only. Setting a region as read only means there's no memstore. No need to flush before move, split, or merge.
> In addition to the wins that Google got, HBase would also be able to shed some memory pressure. Right now every region gets a memstore and with that memstore comes a mslab. Read only regions would not need these added object. This should allow a regionserver to host lots of cold regions without too much memory pressure.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)