[
https://issues.apache.org/jira/browse/HBASE-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HBASE-10569:
----------------------------------
Release Note:
With this patch, HMaster is also a HRegionServer. Active master serves table
META, namespace, and ACL in a secure installation. Backup masters are
regionservers too. They serve regions, while trying to be the next active
master. Once a backup master becomes the active one, it will serve META and
namespace table. Load balancer will move user regions to other regionservers.
HMaster and HRegionServer share the same RPC server. That's transparent to
clients since the master information is in ZK. The master and the regionserver
also shares the same web UI server.
There is no protocol, or API change. So this feature is backward compatible,
and rolling upgradable. In case it's needed, some configurations (HBASE-10815)
will be added so that (1) we can have two web UI servers in the master (and
backup masters), one for the master, and the other for the region server; (2)
we can leave backup masters alone and don't put any regions on them. So that
things are the same as before.
With this patch, the following configurations are removed (and not used any
more):
hbase.master.dns.interface
hbase.master.dns.nameserver
hbase.master.port
hbase.master.ipc.address
hbase.master.zksession.recover.timeout
fail.fast.expired.active.master
hbase.master.handler.count
was:
With this patch, HMaster is also a HRegionServer. Active master serves table
META, namespace, and ACL in a secure installation. Backup masters are
regionservers too. They server regions, while trying to be the next active
master. Once a backup master becomes the active one, it will server META and
namespace table. Load balancer will move user regions to other regionservers.
HMaster and HRegionServer share the same RPC server. That's transparent to
clients since the master information is in ZK. The master and the regionserver
also shares the same web UI server.
There is no protocol, or API change. So this feature is backward compatible,
and rolling upgradable. In case it's needed, some configurations (HBASE-10815)
will be added so that (1) we can have two web UI servers in the master (and
backup masters), one for the master, and the other for the region server; (2)
we can leave backup masters alone and don't put any regions on them. So that
things are the same as before.
With this patch, the following configurations are removed (and not used any
more):
hbase.master.dns.interface
hbase.master.dns.nameserver
hbase.master.port
hbase.master.ipc.address
hbase.master.zksession.recover.timeout
fail.fast.expired.active.master
hbase.master.handler.count
> Co-locate meta and master
> -------------------------
>
> Key: HBASE-10569
> URL: https://issues.apache.org/jira/browse/HBASE-10569
> Project: HBase
> Issue Type: Improvement
> Components: master, Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Fix For: 0.99.0
>
> Attachments: hbase-10569_v1.patch, hbase-10569_v2.patch,
> hbase-10569_v3.1.patch, hbase-10569_v3.patch
>
>
> I was thinking simplifying/improving the region assignments. The first step
> is to co-locate the meta and the master as many people agreed on HBASE-5487.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
