[jira] [Commented] (HBASE-24388) Introduce a 'local root region' at master side to store the location of meta table
[ https://issues.apache.org/jira/browse/HBASE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17114559#comment-17114559 ] Anoop Sam John commented on HBASE-24388: bq.And if so, we could also make the data directory on root fs and the wal directory on wal fs, then the code could be simplified a bit. I was about to ask this Q following Stack's Q.. :-). I have to have a detailed look at this but why this change will simplify the code? Its just a matter of where (which FS) the dir is created right? So it should be a matter of changing the base directory alone? May be am wrong as I did not read the code part. But is that suggest we need better abstraction in code level there? How hard it will be to make this configurable even? (To have the local region data in root or WAL FS) I would say it will be better to rename the 'MasterProcs' to a generic name. > Introduce a 'local root region' at master side to store the location of meta > table > -- > > Key: HBASE-24388 > URL: https://issues.apache.org/jira/browse/HBASE-24388 > Project: HBase > Issue Type: Sub-task > Components: meta, Region Assignment >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24388) Introduce a 'local root region' at master side to store the location of meta table
[
https://issues.apache.org/jira/browse/HBASE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17112228#comment-17112228
]
Duo Zhang commented on HBASE-24388:
---
{quote}
Can we use the existing Region, the Procedure Store Region, and not introduce a
new Region?
{quote}
I‘m neutral on this. Maybe we could introduce something like 'master local
storage', to store all the data, such as procedures and root table.
But if want to do this, then we must do it before shipping out 2.3.0, as in
2.3.0, the region will be stored in a directory called MasterProcs, which is
not a good name for general storage...
And if so, we could also make the data directory on root fs and the wal
directory on wal fs, then the code could be simplified a bit.
I've open a PR for HBASE-24388, PTAL.
https://github.com/apache/hbase/pull/1746
If we want to unify the storage for root table and procedure store, then I will
open another PR to include part of the code in the PR for HBASE-24388, where we
abstract a 'LocalRegion' for storing data, for branch-2.3+.
Thanks.
> Introduce a 'local root region' at master side to store the location of meta
> table
> --
>
> Key: HBASE-24388
> URL: https://issues.apache.org/jira/browse/HBASE-24388
> Project: HBase
> Issue Type: Sub-task
> Components: meta, Region Assignment
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24388) Introduce a 'local root region' at master side to store the location of meta table
[ https://issues.apache.org/jira/browse/HBASE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110757#comment-17110757 ] Michael Stack commented on HBASE-24388: --- Can we use the existing Region, the Procedure Store Region, and not introduce a new Region? > Introduce a 'local root region' at master side to store the location of meta > table > -- > > Key: HBASE-24388 > URL: https://issues.apache.org/jira/browse/HBASE-24388 > Project: HBase > Issue Type: Sub-task > Components: meta, Region Assignment >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24388) Introduce a 'local root region' at master side to store the location of meta table
[ https://issues.apache.org/jira/browse/HBASE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109747#comment-17109747 ] Duo Zhang commented on HBASE-24388: --- I think at beginning we can only query the active master, but this can be changed later. For querying meta location on zk through masters, the masters just act as a cache for zk, so I think backup masters could also act as a cache for the active master. Can do this in later patches. > Introduce a 'local root region' at master side to store the location of meta > table > -- > > Key: HBASE-24388 > URL: https://issues.apache.org/jira/browse/HBASE-24388 > Project: HBase > Issue Type: Sub-task > Components: meta, Region Assignment >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24388) Introduce a 'local root region' at master side to store the location of meta table
[ https://issues.apache.org/jira/browse/HBASE-24388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17109588#comment-17109588 ] Anoop Sam John commented on HBASE-24388: In master branch, now we have MasterRegistry where the META location is available at every HM (Active, Standby). Now when we have the root region which will be having the META regions info, if that is available only in Active HM, that will against this other solution's direction (?). Just raised for a brain storming. > Introduce a 'local root region' at master side to store the location of meta > table > -- > > Key: HBASE-24388 > URL: https://issues.apache.org/jira/browse/HBASE-24388 > Project: HBase > Issue Type: Sub-task > Components: meta, Region Assignment >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
