hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15073) Finer grained control over normalization actions for RegionNormalizer
Date Wed, 27 Jan 2016 18:42:39 GMT

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

Jonathan Hsieh commented on HBASE-15073:
----------------------------------------

The 1.x releases are supposed to be rock solid, and only ideally only add features that have
gone through some bake time and hardening.  This concern was brought up with a long list of
other features on previous versions as well -- for example, mob, distributed log reply, snapshots,
and replication.  

I'm much for receptive to an argument for on by default in 2.x/master -- there new defaults
and bigger changes are to be expected.


> Finer grained control over normalization actions for RegionNormalizer
> ---------------------------------------------------------------------
>
>                 Key: HBASE-15073
>                 URL: https://issues.apache.org/jira/browse/HBASE-15073
>             Project: HBase
>          Issue Type: Task
>          Components: regionserver
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>         Attachments: 15073-v1.txt, 15073-v2.txt, 15073-v2.txt, 15073-v3.txt, 15073-v4.txt,
15073-v5.txt
>
>
> Currently both region split and merge actions are carried out during normalization for
underlying table.
> However, for certain use case(s) (see https://issues.apache.org/jira/browse/HBASE-13103?focusedCommentId=14366255&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14366255‚Äč),
it would be desirable to perform only one type of action.
> There is one boolean flag, keyed by NORMALIZATION_ENABLED_KEY, per table that enables
normalization.
> To provide finer grained control, we have several options:
> 1. introduce another per table flag to indicate which type(s) of actions are allowed
("N" for disabled, "S" for split only, "M" for merge only and "MS" for both split and merge)
> 2. introduce another global flag to indicate which type(s) of actions are allowed
> 3. modify the meaning of existing flag keyed by NORMALIZATION_ENABLED_KEY so that it
indicates type(s) of actions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message