phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <>
Subject [jira] [Updated] (PHOENIX-3482) Provide a work around for HBASE-17096
Date Wed, 16 Nov 2016 23:47:59 GMT


Samarth Jain updated PHOENIX-3482:
    Attachment: PHOENIX-3482.patch

[~jamestaylor], please review. I am not sure if having separate code path for different HBase
versions is worth it. So I took the approach of doing two different checkAndPut calls in acquireUpgradeMutex().

> Provide a work around for HBASE-17096
> -------------------------------------
>                 Key: PHOENIX-3482
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>         Attachments: PHOENIX-3482.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

View raw message