[
https://issues.apache.org/jira/browse/HBASE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109400#comment-15109400
]
Ted Yu commented on HBASE-15073:
--------------------------------
With DEBUG logging on, I observed interleaving region splitting / merge
operations.
e.g.
{code}
2016-01-20 13:09:48,432 INFO
[perf-a-2.c.pramod-thangali.internal,61300,1453265375538_ChoreService_1]
normalizer.SplitNormalizationPlan: Executing splitting normalization plan:
SplitNormalizationPlan{regionInfo={ENCODED => be05e5ebc6d4c10a1df4846c654bb047,
NAME =>
'METRIC_RECORD,bytes_out\x00perf-b-5.c.pramod-thangali.internal\x00\x00\x00\x01R#\xD8\x7F8HOST,1453267789291.be05e5ebc6d4c10a1df4846c654bb047.',
STARTKEY =>
'bytes_out\x00perf-b-5.c.pramod-thangali.internal\x00\x00\x00\x01R#\xD8\x7F8HOST',
ENDKEY =>
'cpu_intr\x00perf-c-386.c.pramod-thangali.internal\x00\x00\x00\x01RU\xBD;yHOST'},
splitPoint=null}
...
2016-01-20 13:19:48,437 INFO
[perf-a-2.c.pramod-thangali.internal,61300,1453265375538_ChoreService_1]
normalizer.MergeNormalizationPlan: Executing merging normalization plan:
MergeNormalizationPlan{firstRegion={ENCODED =>
0115dfae93a4974e09cea8acaa62e69b, NAME =>
'METRIC_RECORD,regionserver.Server.FlushTime_num_ops\x00perf-c-477.c.pramod-thangali.internal\x00\x00\x00\x01R&A\xF3dhbase,1452432082120.0115dfae93a4974e09cea8acaa62e69b.',
STARTKEY =>
'regionserver.Server.FlushTime_num_ops\x00perf-c-477.c.pramod-thangali.internal\x00\x00\x00\x01R&A\xF3dhbase',
ENDKEY =>
'regionserver.Server.Mutate_min\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'},
secondRegion={ENCODED => be8228be1ed0cb686bbc5d6958c5c2f1, NAME =>
'METRIC_RECORD,regionserver.Server.Mutate_min\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00,1452372244525.be8228be1ed0cb686bbc5d6958c5c2f1.',
STARTKEY =>
'regionserver.Server.Mutate_min\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00',
ENDKEY =>
'regionserver.Server.blockedRequestCount\x00perf-c-48.c.pramod-thangali.internal\x00\x00\x00\x01R!%\xA8=hbase'}}
{code}
So far the number of regions for METRIC_RECORD table is stable at 38 regions.
> 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)
