[
https://issues.apache.org/jira/browse/HBASE-17743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899978#comment-15899978
]
stack commented on HBASE-17743:
-------------------------------
[~carp84] Looks great. Just to say that work already by-passing RPC in
particular when Master was hosting hbase:meta. Let me know if you need
pointers.
You've seen RegionAsTable class? You talking of an embedded instance running
with more than one table? Would it be too radical doing one table per embedded
instance? Could then just add a main on RegionAsTable then (smile).
> 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)
