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-3482) Provide a work around for HBASE-17096
Date Thu, 17 Nov 2016 09:44:59 GMT

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

Hudson commented on PHOENIX-3482:
---------------------------------

FAILURE: Integrated in Jenkins build Phoenix-master #1495 (See [https://builds.apache.org/job/Phoenix-master/1495/])
PHOENIX-3482 Addendum to fix the test failure (Samarth: rev f1ecd4f7d809c037c8b716672faf5f3b6f3d452f)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/UpgradeIT.java


> Provide a work around for HBASE-17096
> -------------------------------------
>
>                 Key: PHOENIX-3482
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3482
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>             Fix For: 4.9.0, 4.8.2
>
>         Attachments: PHOENIX-3482.patch, PHOENIX-3482_v2.patch
>
>
> HBASE-17096 causes failures in UpgradeIT#testAcquiringAndReleasingUpgradeMutex. Essentially
releasing of the upgrade mutex by using the checkAndMutate api isn't working correctly. A
simple though not ideal work around would be to not call releaseMutex() and let the lock expire
by the virtue of TTL set on the cell. The side effect is that if a client encounters and exception
while executing the upgrade code, then a new client won't be able to initiate the upgrade
till the TTL expires.  



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

Mime
View raw message