[
https://issues.apache.org/jira/browse/HBASE-9637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Liochon resolved HBASE-9637.
------------------------------------
Resolution: Duplicate
Yes. It's seems to be a duplicate of HBASE-6773 (but note that a patch is
welcome :-) ).
> HBase internal (ROOT and META) tables replication factor configuration apart
> from the user table data
> -----------------------------------------------------------------------------------------------------
>
> Key: HBASE-9637
> URL: https://issues.apache.org/jira/browse/HBASE-9637
> Project: HBase
> Issue Type: New Feature
> Components: master, regionserver
> Reporter: shankarlingayya
> Priority: Minor
>
> {noformat}
> HBase has two types of data
> 1. Internal data (ROOT & META tables)
> 2. User loaded table data
> For accessing the HBase user data we must have ROOT & META, assume that
> the nodes in which ROOT & META table are down/not accessible (assuming 3
> replication factor) all the 3 nodes went down.
> Now the entire HBase system in not accessible (user data will be TB, while
> ROOT & META Table will be few MB)
> so, it is better we can have the flexibility of configuring the more
> replication for Internal Table (ROOT & META)
> Already we have the replication configuration in HBase but the problem with
> that is it is for both internal table (ROOT. META) & also for User Table
> data..
> Since user data willl be in TB so, increasing the replication will consume
> huge space for user which is not feasible.
> So it is better and safe to have more replication of only the Internal tables
> (ROOT, META) by giving sepecate configurable parameter to user.
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
