Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sat, 21 Jan 2017 17:10:26 +0000 (UTC)
From: "Eugene Koifman (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12937107.1454696166000.70436.1485018626461@Atlassian.JIRA>
In-Reply-To: <JIRA.12937107.1454696166000@Atlassian.JIRA>
References: <JIRA.12937107.1454696166000@Atlassian.JIRA> <JIRA.12937107.1454696166306@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HIVE-13014) RetryingMetaStoreClient is retrying
 acid related calls too aggresievley
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sat, 21 Jan 2017 17:10:36 -0000


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

Eugene Koifman updated HIVE-13014:
----------------------------------
    Summary: RetryingMetaStoreClient is retrying acid related calls too aggresievley  (was: RetryingMetaStoreClient is retrying too aggresievley)

> RetryingMetaStoreClient is retrying acid related calls too aggresievley
> -----------------------------------------------------------------------
>
>                 Key: HIVE-13014
>                 URL: https://issues.apache.org/jira/browse/HIVE-13014
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Transactions
>    Affects Versions: 1.0.0
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>            Priority: Critical
>         Attachments: HIVE-13014.01.patch, HIVE-13014.02.patch, HIVE-13014.03.patch, HIVE-13014.04.patch, HIVE-13014.05.patch, HIVE-13014.06.patch, HIVE-13014.07.patch
>
>
> Not all metastore operations are idempotent.  For example, commit_txn() consists of 
> 1. request from client to server
> 2. server action
> 3. ack to client
> If network connection is broken after (or during) 2 but before 3 happens, RetryingMetastoreClient will retry the operation thus causing an attempt to commit the same txn twice (sometimes in concurrently)
> The 2nd attempt is guaranteed to fail and thus return an error to the caller (which doesn't know the operation is being retried), while the first attempt has actually succeeded.  Thus the caller thinks commit failed and will likely attempt to redo the transactions - not what we want in most cases.


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