hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15073) Finer grained control over normalization actions for RegionNormalizer
Date Sun, 17 Jan 2016 01:01:51 GMT

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

stack commented on HBASE-15073:
-------------------------------

I'm trying to trace the new 'normalization' feature.

What is this about?

bq. However, for certain use case(s), it would be desirable to perform only one type of action.

A statement about 'cases' but no cases are provided.

Why do we need finer grained control? The point is that this is an ergonomic feature that
lets the machine do it for you... if need admin intervention, then the feature is not working
right... lets fix that. This issue seems to mangle the intent of 'normalization'.

Looking at patch I see a define: DESIRED_NORMALIZATION_TYPES  What does DESIRED mean? This
is a datastore, not a beach at sunset...

Users are going to see 'MS', 'M', and 'S' and are supposed to get split, merge, etc. from
this? That's not nice on our user.

I'm -1 on this thing till its explained why.  I think should revert from 1.2.  Reopening.



> 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
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         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), 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