hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jimmy Xiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10815) Master regionserver should be rolling-upgradable
Date Sun, 30 Mar 2014 15:42:15 GMT

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

Jimmy Xiang commented on HBASE-10815:

How about we file two followup and let this patch in (add the new configuration parameters
in hbase-default.xml, enable backup masters to host regions by default)? One followup  is
to fix the infoserver. The other followup is to make StochasticLoadBalancer adjustable so
that we can tune the number of regions to assign to each backup master, since it's better
to be in a separate jira.

> 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

View raw message