phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3535) Fix race condition in ConnectionQueryServicesImpl#acquireUpgradeMutex
Date Thu, 22 Dec 2016 03:07:58 GMT

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

Hudson commented on PHOENIX-3535:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-master #1520 (See [https://builds.apache.org/job/Phoenix-master/1520/])
PHOENIX-3535 Addendum to fix test failures (samarth: rev 108b78deed29b42b9a37470abb8e832108182361)
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java


> Fix race condition in ConnectionQueryServicesImpl#acquireUpgradeMutex
> ---------------------------------------------------------------------
>
>                 Key: PHOENIX-3535
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3535
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>             Fix For: 4.9.1, 4.10.0
>
>         Attachments: PHOENIX-3535_v1.patch, PHOENIX-3535_v2.patch
>
>
> Conversation on HBASE-17300 revealed that concurrently creating a table, checking for
its existence and performing an operation on it is fraught with races. This race condition
is causing UpgradeIT#testConcurrentUpgradeThrowsUpgradeInProgressException to fail. We need
to figure out a way for not creating/checking existence of the SYSTEM.MUTEX table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message