[
https://issues.apache.org/jira/browse/HBASE-11288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118217#comment-17118217
]
Guanghao Zhang commented on HBASE-11288:
----------------------------------------
I thought we are consistent on this point: need a splittable meta and need a
storage to store the meta regions location (more than 1). Then we have three
choices now:
# zk node
# root table
# master local region
For zk node, we want to reduce zk dependency, so this is not a good choice?
For root table, I thought the previous problems about meta table will become
the problems about root table. root table should be splitable? If root table
cannot splitable, which regionserver to host root table's region, a isolated
region or share with user regions? In our production use case (300+
RegionServer, 200K+ Regions, 1K+ tables), the meta region is isolated on one
regionserver, not share with the user regions. This is a waste of machine, but
for better stability. And we have many hack logic for meta regions, such as
assign meta first, donot replicate meta wal, balancer give a bigger weight for
meta region, the new root table need all these hack, too? You can found these
by grep isMetaTable or isMetaRegion calls in our codebase...
For master local region, the master was light load so we use small heap for
master. And deploy many master on one share machine. There may be many locate
request when many client bootstrap or failover? This is a challange for master.
In our production use case , we meet one case is too many regionserver report
slow down master... Another problem is the availability of master. In the past,
master didn't response user access request so the lower availability is not a
big deal. We can restart master at any time. In a big cluser, the master
bootstrap may take almost 1 minute to load all things from zookeeper or meta
table or receive the report from regionserver. But if master serve the root
table, it may need higher availability.
> Splittable Meta
> ---------------
>
> Key: HBASE-11288
> URL: https://issues.apache.org/jira/browse/HBASE-11288
> Project: HBase
> Issue Type: Umbrella
> Components: meta
> Reporter: Francis Christopher Liu
> Assignee: Francis Christopher Liu
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
