hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-13014) RetryingMetaStoreClient is retrying too aggresievley
Date Tue, 31 May 2016 19:53:13 GMT

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

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

[~ekoifman], I am removing 2.1.0 as target because the RC will be created tomorrow. Please
feel free to commit to branch-2.1 anyway and fix for 2.1.0 if this happens before the release,
or let me know if this is a Blocker. 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)

Mime
View raw message