You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Samarth Jain (JIRA)" <ji...@apache.org> on 2017/09/01 00:48:01 UTC

[jira] [Resolved] (PHOENIX-4143) ConcurrentMutationsIT flaps

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

Samarth Jain resolved PHOENIX-4143.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 4.12.0

> 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
>             Fix For: 4.12.0
>
>         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)