phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4176) Reduce chances of tests flapping with ColumnFamilyNotFoundException for HBase 1.x
Date Thu, 07 Sep 2017 06:05:00 GMT

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

James Taylor commented on PHOENIX-4176:
---------------------------------------

Can we put a different check in the code that adds a cf? Or in base scanner coprocessor? Maybe
[~lhofhansl] has ideas?

> 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
>
>
> 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)

Mime
View raw message