hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sushanth Sowmyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10507) Expose RetryingMetastoreClient to other external users of metastore client like Flume and Storm.
Date Wed, 29 Apr 2015 21:58:08 GMT

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

Sushanth Sowmyan commented on HIVE-10507:
-----------------------------------------

Although we've passed the deadline for feature inclusions, this is more a clarification, and
a trivial one at that - I can make an exception for this. Please note that if you have any
further jiras like this, please do check with me asap, because after tomorrow 15:01 PDT, I
will be more strict in accepting patches of all sorts as we increase the severity bar for
inclusion then.

I've added this to https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status

> Expose  RetryingMetastoreClient to other external users of metastore client like Flume
and Storm.
> -------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-10507
>                 URL: https://issues.apache.org/jira/browse/HIVE-10507
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Hari Sankar Sivarama Subramaniyan
>            Assignee: Hari Sankar Sivarama Subramaniyan
>         Attachments: HIVE-10507.1.patch
>
>
> HiveMetastoreClient is now being relied upon by external clients like Flume and Storm
for streaming.
> When the thrift connection between MetaStoreClient and the meta store is broken (due
to intermittent network issues or restarting of metastore) the Metastore does not handle the
connection error and automatically re-establish the connection. Currently the client process
needs to be restarted to re-establish the connection.
> The request here is consider supporting the following behavior: For each API invocation
on the MetastoreClient, it should try to restablish the connection (if needed) once. And if
that does not work out then throw a specific exception indicating the same. The client could
then handle the issue by retrying the same API after some delay. By catching the specific
connection exception, the client could decide how many times to retry before aborting.
> Hive does this internally using RetryingMetastoreClient. This jira is suppose to expose
this mechanism to other users of that interface. This is useful for users of this interface,
and from metastore HA point of view.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message