Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 31 Mar 2014 17:09:15 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12703241.1395679451169.37315.1396285755410@arcas>
In-Reply-To: <JIRA.12703241.1395679451169@arcas>
References: <JIRA.12703241.1395679451169@arcas>
Subject: [jira] [Updated] (HBASE-10815) Master regionserver should be
 rolling-upgradable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jimmy Xiang updated HBASE-10815:
--------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

> Master regionserver should be rolling-upgradable
> ------------------------------------------------
>
>                 Key: HBASE-10815
>                 URL: https://issues.apache.org/jira/browse/HBASE-10815
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, Region Assignment
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>             Fix For: 0.99.0
>
>         Attachments: hbase-10815.patch, hbase-10815_v2.patch
>
>
> In HBASE-10569, two things could affect the rolling-upgrade from a 0.96+ release:
> * Master doesn't have its own info server any. It shares the same info server with the regionserver. We can have a setting so that we can start two info servers, one for the master on the original port, and one for the regionserver.
> * Backup master is a regionserver now. So it could hold regions. This could affect some deployment. We can have a setting so that we can prevent backup master from serving any region.


--
This message was sent by Atlassian JIRA
(v6.2#6252)