[
https://issues.apache.org/jira/browse/HBASE-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Xiang updated HBASE-10815:
--------------------------------
Attachment: hbase-10815.patch
Attached the first patch. It is on RB: https://reviews.apache.org/r/19759/
In the patch, two configurations are added to control if we assign regions to
backup masters, and if we start two info servers in M+RS.
In order to reliably not assigning regions to backup masters if so configured,
we changed a little on how master create the backup znode, and how server
manager adds new server.
> 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
>
>
> 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)
