phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2249) SYSTEM.STATS not update after region merge occurs.
Date Sun, 13 Dec 2015 07:43:46 GMT


Hadoop QA commented on PHOENIX-2249:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit afa9dee2be618cca8bd43a11311aea2062fa551c.
  ATTACHMENT ID: 12777335

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> SYSTEM.STATS not update after region merge occurs.
> --------------------------------------------------
>                 Key: PHOENIX-2249
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>         Environment: Ubuntu server 14.04
> Hadoop 2.6.0
> HBase 1.0.0
> Phoenix 4.4.0-HBase-1.0.0
>            Reporter: Kuan-Po Tseng
>            Assignee: Ankit Singhal
>             Fix For: 4.7.0
>         Attachments: PHOENIX-2249.patch, PHOENIX-2249_V1.patch, PHOENIX-2249_v2_4.x-0.98.patch,
> When region merge occurs, SYSTEM.STATS does not update, it will leave stale information
behind. And then if region splits on the merged region, this may cause 
> "org.apache.phoenix.schema.StaleRegionBoundaryCacheException: ERROR 1108 (XCL08): Cache
of region boundaries are out of date" 
> after creating parallel scans since the stale information in SYSTEM.STATS will let guide
post list not sorted in ascending order and this will cause scans over regions.

This message was sent by Atlassian JIRA

View raw message