You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/16 00:30:46 UTC

[jira] [Commented] (HBASE-14055) Untangle region - region server dependencies

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

stack commented on HBASE-14055:
-------------------------------

Interested in getting this in [~enis] I like the WALServices bit...  Or, would it be better to put up a target for where to take Region long term first to make sure this patch and others are driving toward it (We have RegionServices Interface but we also have Region Interface... we need both?)

> Untangle region - region server dependencies
> --------------------------------------------
>
>                 Key: HBASE-14055
>                 URL: https://issues.apache.org/jira/browse/HBASE-14055
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0, 1.3.0
>
>         Attachments: hbase-14055_v1.patch
>
>
> We need to untangle region from outside of region server. The parent jira is trying to create an embedded library, like leveldb, out of region so that it should be possible to host a set of regions without being a regionserver. 
> From a layering point of view, region hosting and WAL services should be abstracted. Hosting a region means threads for flushing, compaction, cleanups, hosting a WAL, and block cache. The RegionServer normally holds these, together with RpcServer and zk connection, heartbeats, and all other stuff that is required for running as a deamon and inside a cluster. 
> See parent jira for some more context. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)