hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Koifman (JIRA)" <>
Subject [jira] [Commented] (HIVE-13014) RetryingMetaStoreClient is retrying too aggresievley
Date Sat, 21 Jan 2017 00:45:27 GMT


Eugene Koifman commented on HIVE-13014:

1. I've not tried to test performance but since Annotations can't change at runtime, I would
think Java/jit should handle it.
2. It probably does, but I wasn't aiming to do a comprehensive analysis of all metastore call
- just Acid related ones.  The title sounds too broad.

> RetryingMetaStoreClient is retrying too aggresievley
> ----------------------------------------------------
>                 Key: HIVE-13014
>                 URL:
>             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
> 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

View raw message