You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2017/03/07 16:19:38 UTC

[jira] [Commented] (HBASE-17743) Support embedded mode in HBase

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

Ted Yu commented on HBASE-17743:
--------------------------------

bq. 	Only one region per database, no assignment, no zookeeper

Can multi-wal be used for multiple regions ?
There would be one region server. All regions are assigned to this server. Can this reduce startup time ?

> Support embedded mode in HBase
> ------------------------------
>
>                 Key: HBASE-17743
>                 URL: https://issues.apache.org/jira/browse/HBASE-17743
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Yu Li
>            Assignee: Yu Li
>         Attachments: Embedded HBase Design.docx
>
>
> Currently HBase supports stand-alone mode and suggest to use it for embedded database requirements, which has below problems:
> 1. HMaster and HRegionServer are still separated threads, which cost more resource
> 2. There’s still RPC cost when doing request, which makes a poor performance
> 3. There're still distributed component involved in standalone-mode, such as zookeeper and DLS, which makes the startup/shutdown speed not acceptable for embedded usage.
> Here we propose to support the embedded mode natively, mainly in two steps:
> 1. Simple embedded mode, which still uses zookeeper for coordination, but with only one server thread and supports access w/o RPC
> 2. Full embedded mode, which removes all distributed stuff and make a clean embedded core for embedded usage.
> Please see more details in the design doc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)