hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18444) Add support for specifying custom meta table suffix
Date Wed, 26 Jul 2017 22:28:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102382#comment-16102382

Sean Busbey commented on HBASE-18444:

Can we get a scope document here?

1) use case motivation. normally our deployment guidance for multiple clusters sharing an
underlying storage source would be to set different root dirs. It sounds like your proposition
is sharing table data. How do the read only clusters properly see updates to that data if
they have their own meta?

2) How are we flagging a cluster as read-only?

3) How do we handle upgrade? Can I turn this on for an existing cluster?

4) How do we explain this for downstream use via documentation?

> Add support for specifying custom meta table suffix
> ---------------------------------------------------
>                 Key: HBASE-18444
>                 URL: https://issues.apache.org/jira/browse/HBASE-18444
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 2.0.0, 1.3.1
>            Reporter: Ajay Jadhav
>            Assignee: Ajay Jadhav
>            Priority: Minor
>              Labels: patch
>             Fix For: 1.4.0
>         Attachments: HBASE-18444.branch-1.001.patch
> This patch provides user an ability to have a custom meta table suffix.
> In order to share a common rootDir amongst multiple HBase clusters, we need separate
meta table for each cluster.
> With custom meta table suffix, the meta table is named in the form of meta_{suffix} making
it specific to a cluster.
> Users can specify the meta table suffix as part of hbase-site.xml.

This message was sent by Atlassian JIRA

View raw message