hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-13643) Follow Google to get more 9's
Date Thu, 07 May 2015 17:05:59 GMT
Elliott Clark created HBASE-13643:
-------------------------------------

             Summary: 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


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. These
writes to meta

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
(v6.3.4#6332)

Mime
View raw message