[
https://issues.apache.org/jira/browse/HBASE-17295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chang chen updated HBASE-17295:
-------------------------------
Description:
>From the codes, hbase namespace meta table should not allowed to be split.
{quote}
public byte[] checkSplit() {
// Can't split META
if (this.getRegionInfo().isMetaTable() ||
TableName.NAMESPACE_TABLE_NAME.equals(this.getRegionInfo().getTable()))
{
if (shouldForceSplit()) {
LOG.warn("Cannot split meta region in HBase 0.20 and above");
}
return null;
}
{quote}
But recently, I see two namespace regions in our production deployment. it
may cased by restart clusters.
> The namespace table has two regions
> -----------------------------------
>
> Key: HBASE-17295
> URL: https://issues.apache.org/jira/browse/HBASE-17295
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Chang chen
> Attachments: bug.PNG
>
>
> From the codes, hbase namespace meta table should not allowed to be split.
> {quote}
> public byte[] checkSplit() {
> // Can't split META
> if (this.getRegionInfo().isMetaTable() ||
>
> TableName.NAMESPACE_TABLE_NAME.equals(this.getRegionInfo().getTable())) {
> if (shouldForceSplit()) {
> LOG.warn("Cannot split meta region in HBase 0.20 and above");
> }
> return null;
> }
> {quote}
> But recently, I see two namespace regions in our production deployment. it
> may cased by restart clusters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
