thrift - How can I trace the failure ot TSaslTransport (hive related) -
i've been debugging jdbc connection error in hive, similar asked here:
hive jdbc getconnection not return.
by turning on log4j properly, got down seeing , before getconnection() hangs. thrift waiting ? if related using wrong thrift apis, how can determine versioning differences between client/server?
i have tried copying libraries hive server onto client app test if kind of minor thrift class versioning error, didnt solve problem, jdbc connection still hangs.
0 [main] debug org.apache.thrift.transport.tsasltransport - opening transport org.apache.thrift.transport.tsaslclienttransport@219ba640 0 [main] debug org.apache.thrift.transport.tsasltransport - opening transport org.apache.thrift.transport.tsaslclienttransport@219ba640 3 [main] debug org.apache.thrift.transport.tsaslclienttransport - sending mechanism name plain , initial response of length 14 3 [main] debug org.apache.thrift.transport.tsaslclienttransport - sending mechanism name plain , initial response of length 14 5 [main] debug org.apache.thrift.transport.tsasltransport - client: writing message status start , payload length 5 5 [main] debug org.apache.thrift.transport.tsasltransport - client: writing message status start , payload length 5 5 [main] debug org.apache.thrift.transport.tsasltransport - client: writing message status complete , payload length 14 5 [main] debug org.apache.thrift.transport.tsasltransport - client: writing message status complete , payload length 14 5 [main] debug org.apache.thrift.transport.tsasltransport - client: start message handled 5 [main] debug org.apache.thrift.transport.tsasltransport - client: start message handled 5 [main] debug org.apache.thrift.transport.tsasltransport - client: main negotiation loop complete 5 [main] debug org.apache.thrift.transport.tsasltransport - client: main negotiation loop complete 6 [main] debug org.apache.thrift.transport.tsasltransport - client: sasl client receiving last message 6 [main] debug org.apache.thrift.transport.tsasltransport - client: sasl client receiving last message
Comments
Post a Comment