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 2017/08/15 04:21:00 UTC

[jira] [Resolved] (HBASE-18154) Verify Master carrying system-tables only with short-circuit RPC

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

stack resolved HBASE-18154.
---------------------------
    Resolution: Not A Problem
      Assignee: stack

Resolving as not a problem. Over in HBASE-18511 I verified we do short-circuit RPC if we've enabled master-carrying-regions. It also adds the called for tests and figures how we are going to deliver master-with-tables vs master-w/o-tables.

> Verify Master carrying system-tables only with short-circuit RPC
> ----------------------------------------------------------------
>
>                 Key: HBASE-18154
>                 URL: https://issues.apache.org/jira/browse/HBASE-18154
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Region Assignment
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> This sort-of-works in new AMv2 given this the current default. Spend some time on it. Ensure that when Master goes down, on relaunch, that it gets the system tables back. Ensure we are doing the short-circuit RPC.
> RegionServer Groups might be the right conduit for this sort of deploy type. Review.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)