phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4143) ConcurrentMutationsIT flaps
Date Fri, 01 Sep 2017 00:45:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Samarth Jain updated PHOENIX-4143:
----------------------------------
    Attachment:     (was: PHOENIX-4132_v2.patch)

> ConcurrentMutationsIT flaps
> ---------------------------
>
>                 Key: PHOENIX-4143
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4143
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-4143.patch, PHOENIX-4143_v2.patch
>
>
> I have seen sometimes that the test flaps with a RegionOpeningException especially on
master and 1.x branches. I believe this is likely because we are adding a co-processor by
doing an admin.modify() call which is asynchronous. So it's possible that the region would
likely be still opening even though the call returned. A potential fix is to poll for the
updated table descriptor. Not sure if it will always prevent test from flapping (since the
problem is similar to what Rajesh is solving in PHOENIX-3496) but it should reduce the chances.
> FYI, [~jamestaylor]



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

Mime
View raw message