You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Xiaobing Zhou (JIRA)" <ji...@apache.org> on 2015/02/25 02:14:05 UTC
[jira] [Updated] (HIVE-9642) Hive metastore client retries don't
happen consistently for all api calls
[ https://issues.apache.org/jira/browse/HIVE-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaobing Zhou updated HIVE-9642:
--------------------------------
Attachment: HIVE-9642.1.patch
Made tentative patch. [~thejas], can you review it? Thanks!
> Hive metastore client retries don't happen consistently for all api calls
> -------------------------------------------------------------------------
>
> Key: HIVE-9642
> URL: https://issues.apache.org/jira/browse/HIVE-9642
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Xiaobing Zhou
> Assignee: Xiaobing Zhou
> Attachments: HIVE-9642.1.patch
>
>
> When org.apache.thrift.transport.TTransportException is thrown for issues like socket timeout, the retry via RetryingMetaStoreClient happens only in certain cases.
> Retry happens for the getDatabase call in but not for getAllDatabases().
> The reason is RetryingMetaStoreClient checks for TTransportException being the cause for InvocationTargetException. But in case of some calls such as getAllDatabases in HiveMetastoreClient, all exceptions get wrapped in a MetaException. We should remove this unnecessary wrapping of exceptions for certain functions in HMC.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)