You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Andrey Stepachev (JIRA)" <ji...@apache.org> on 2014/03/03 14:45:21 UTC
[jira] [Updated] (HIVE-6427) Hive Server2 should reopen Metastore
client in case of any Thrift exceptions
[ https://issues.apache.org/jira/browse/HIVE-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Stepachev updated HIVE-6427:
-----------------------------------
Attachment: 0001-HDPDEV-53-HiveServer-should-reconnect-automatically-.patch
Patch was updated.
> Hive Server2 should reopen Metastore client in case of any Thrift exceptions
> ----------------------------------------------------------------------------
>
> Key: HIVE-6427
> URL: https://issues.apache.org/jira/browse/HIVE-6427
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Affects Versions: 0.12.0
> Environment: cloudera cdh5 beta2
> Reporter: Andrey Stepachev
> Priority: Critical
> Attachments: 0001-HDPDEV-53-HiveServer-should-reconnect-automatically-.patch, 0001-HIVE-6427-Hive-Server2-should-reopen-Metastore-clien.patch
>
>
> In case of metastore restart hive server doesn't reopen connection to metastore. Any command gives broken pipe or similar exceptions.
> http://paste.ubuntu.com/6926215/
> Any subsequent command doesn't reestablish connection and tries to use stale (closed) connection.
> Looks like we shouldn't blindly convert any MetaException to HiveSQLException, but should distinguish between fatal exceptions and logical exceptions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)