[jira] [Comment Edited] (PHOENIX-4176) Reduce chances of tests flapping with ColumnFamilyNotFoundException for HBase 1.x

["Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org>]

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

Rajeshbabu Chintaguntla edited comment on PHOENIX-4176 at 9/7/17 6:49 AM:
--------------------------------------------------------------------------

[~samarthjain] FYI as part of PHOENIX-3496 exactly solving the same problem. Just retrying opening scanner until the column family added. May be same thing helps in case of modifying column family cases as well with minimal changes.


was (Author: rajeshbabu):
[~samarthjain] FYI as part of PHOENIX-3496 exactly solving the same problem. Just retrying opening scanner until the column family added. May be same thing helps in case of modifying column family cases as well.

> Reduce chances of tests flapping with ColumnFamilyNotFoundException for HBase 1.x
> ---------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4176
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4176
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-4176.patch, PHOENIX-4176_v2.patch
>
>
> In HBase 1.x, when adding a new column family, the check to detect whether the HTableDescriptor is updated isn't enough. Tests that add a new column family run the risk of flapping when number of regions on the table are high (since the column family has to be added to all the regions). Till we figure out a permanent solution for this, we can possibly decrease chances of such tests from flapping by reducing number of regions/pre-splits and possibly configuring hbase.online.schema.update.enable to false in our tests. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)