hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (Commented) (JIRA)" <>
Subject [jira] [Commented] (HIVE-2883) Metastore client doesnt close connection properly
Date Wed, 04 Apr 2012 18:25:24 GMT


Ashutosh Chauhan commented on HIVE-2883:

My analysis is client already knows about transport, so inside client.shutdown() it is calling
transport.close() which closes underlying outputstream. So, we *should* not do transport.close()
ourselves in HiveMetaStoreClient.close() ? But, I can't be sure of this hypothesis since implementation
of client.shutdown() is in FaceBookService.client (which is in libfb303.jar) I cant seem to
find sources for this class anywhere. 

So, I request Facebook contributors of Hive project to either fix this bug or release sources
of libfb303.jar so that I can verify and fix this myself.
> Metastore client doesnt close connection properly
> -------------------------------------------------
>                 Key: HIVE-2883
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.9.0
>            Reporter: Ashutosh Chauhan
>             Fix For: 0.9.0
> While closing connection, it always fail with following trace. Seemingly, it doesnt have
any harmful effects.
> {code}
> 12/03/20 10:55:02 ERROR hive.metastore: Unable to shutdown local metastore client
> org.apache.thrift.transport.TTransportException: Cannot write to null outputStream
> 	at org.apache.thrift.transport.TIOStreamTransport.write(
> 	at org.apache.thrift.protocol.TBinaryProtocol.writeI32(
> 	at org.apache.thrift.protocol.TBinaryProtocol.writeMessageBegin(
> 	at org.apache.thrift.TServiceClient.sendBase(
> 	at com.facebook.fb303.FacebookService$Client.send_shutdown(
> 	at com.facebook.fb303.FacebookService$Client.shutdown(
> 	at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.close(
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message