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 2016/12/16 20:46:58 UTC
[jira] [Updated] (PHOENIX-3535) Fix race condition in
ConnectionQueryServicesImpl#acquireUpgradeMutex
[ https://issues.apache.org/jira/browse/PHOENIX-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samarth Jain updated PHOENIX-3535:
----------------------------------
Attachment: PHOENIX-3535_v1.patch
v1 patch that creates the sys mutex table at the start of init(). This reduces chances of race condition but doesn't completely fix it.
> 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
> Attachments: PHOENIX-3535_v1.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)