如何跟踪TSaslTransport（与hive相关）的故障

Question

我在hive中调试了JDBC连接错误，类似于此处提到的错误：

Hive JDBC getConnection does not return

通过正确启用log4j，我终于在getConnection（）挂起之前就看到了这一点。什么是节俭等待？如果这与使用错误的thrift API有关，我如何确定客户端/服务器之间的版本差异？

我已经尝试将我的hive服务器中的所有库复制到我的客户端应用程序上以测试它是否是某种轻微的thrift类版本控制错误，但是这并没有解决问题，我的JDBC连接仍然挂起。

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 and initial response of length 14 3 [main] DEBUG org.apache.thrift.transport.TSaslClientTransport - Sending mechanism name PLAIN and initial response of length 14 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status START and payload length 5 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status START and payload length 5 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status COMPLETE and payload length 14 5 [main] DEBUG org.apache.thrift.transport.TSaslTransport - CLIENT: Writing message with status COMPLETE and 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