Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Sat, 24 Sep 2016 00:33:20 +0000 (UTC)
From: "Samarth Jain (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13007231.1474657241000.654201.1474677200609@Atlassian.JIRA>
In-Reply-To: <JIRA.13007231.1474657241000@Atlassian.JIRA>
References: <JIRA.13007231.1474657241000@Atlassian.JIRA> <JIRA.13007231.1474657241092@arcas>
Subject: [jira] [Updated] (PHOENIX-3326) Restoring SYSTEM.CATALOG from
 snapshot causes clients to run into UpgradeInProgressException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 24 Sep 2016 00:33:22 -0000


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

Samarth Jain updated PHOENIX-3326:
----------------------------------
    Attachment: PHOENIX-3326_4.8-HBase-0.98_v2.patch

> Restoring SYSTEM.CATALOG from snapshot causes clients to run into UpgradeInProgressException
> --------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-3326
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3326
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Samarth Jain
>         Attachments: PHOENIX-3326_4.8-HBase-0.98.patch, PHOENIX-3326_4.8-HBase-0.98_v2.patch, PHOENIX-3326_wip.patch
>
>
> We create a snapshot of the SYSTEM.CATALOG table only after the client is able to successfully acquire a distributed mutex of sorts. This means the snapshot also ends up containing the row that serves as the mutex. Now when restoring the table from snapshot, this rows is still present which causes clients to throw UpgradeInProgress exception. 
> I can think of a couple of ways to fix this:
> 1) Do the checkAndPut for the UPGRADE_MUTEX after creating the snapshot. I am not too sure though how about HBase handles concurrent snapshot requests. Do clients get an exception? Also we potentially could end up creating more snapshots than we really need to. 
> 2) Do the checkAndPut for the UPGRADE_MUTEX in a different table (possibly SYSTEM.SEQUENCE). This way the restored snapshot won't have the row. We would need to delete the row from SYSTEM.SEQUENCE after the upgrade is done (successfully or unsuccessfully).
> [~jamestaylor] - WDYT? 
> FYI, [~lhofhansl] - this is probably a blocker for 4.8.1


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