You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2016/05/25 11:34:12 UTC

[jira] [Commented] (HIVE-13014) RetryingMetaStoreClient is retrying too aggresievley

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

Jesus Camacho Rodriguez commented on HIVE-13014:
------------------------------------------------

[~ekoifman], this is marked as Critical. Will it go into 2.1.0? Thanks

> RetryingMetaStoreClient is retrying 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
>
> 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)