[IMPALA-10120] Beeline hangs when connecting to coordinators

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: Impala 4.4.0
• Component/s: Clients
• Epic Color: ghx-label-1
• Assignee: XiangYang
• Reporter: Quanlong Huang
• Created: 01/Sep/20 08:45
• Updated: 25/Oct/23 15:41
• Resolved: 25/Oct/23 15:41

Description

Beeline is always hanging when connecting to a coordinator:

$ beeline -u "jdbc:hive2://localhost:21050/default;auth=noSasl"
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/quanlong/workspace/Impala/toolchain/cdp_components-4493826/apache-hive-3.1.3000.7.2.1.0-287-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/quanlong/workspace/Impala/toolchain/cdp_components-4493826/hadoop-3.1.1.7.2.1.0-287/share/hadoop/common/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/quanlong/workspace/Impala/toolchain/cdp_components-4493826/apache-hive-3.1.3000.7.2.1.0-287-bin/lib/log4j-slf4j-impl-2.10.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/quanlong/workspace/Impala/toolchain/cdp_components-4493826/hadoop-3.1.1.7.2.1.0-287/share/hadoop/common/lib/slf4j-log4j12-1.7.30.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
Connecting to jdbc:hive2://localhost:21050/default;auth=noSasl
Connected to: Impala (version 4.0.0-SNAPSHOT)
Driver: Hive JDBC (version 3.1.3000.7.2.1.0-287)
Transaction isolation: TRANSACTION_REPEATABLE_READ

Looking into the impalad log file, there is a wrong option set:

I0901 15:41:14.577576 25325 TAcceptQueueServer.cpp:340] New connection to server hiveserver2-frontend from client <Host: ::ffff:127.0.0.1 Port: 51776>
I0901 15:41:14.577911 25597 impala-hs2-server.cc:300] Opening session: 204a3f33cc8e28ea:d6a915ab96b26aa7 request username: 
I0901 15:41:14.577970 25597 status.cc:129] Invalid query option: set:hiveconf:hive.server2.thrift.resultset.default.fetch.size
    @          0x1cdba3d  impala::Status::Status()
    @          0x24c673f  impala::SetQueryOption()
    @          0x250c1d1  impala::ImpalaServer::OpenSession()
    @          0x2b0dc45  apache::hive::service::cli::thrift::TCLIServiceProcessor::process_OpenSession()
    @          0x2b0d993  apache::hive::service::cli::thrift::TCLIServiceProcessor::dispatchCall()
    @          0x2acd15a  impala::ImpalaHiveServer2ServiceProcessor::dispatchCall()
    @          0x1c8a483  apache::thrift::TDispatchProcessor::process()
    @          0x218ab4a  apache::thrift::server::TAcceptQueueServer::Task::run()
    @          0x218004a  impala::ThriftThread::RunRunnable()
    @          0x2181686  boost::_mfi::mf2<>::operator()()
    @          0x218151a  boost::_bi::list3<>::operator()<>()
    @          0x2181260  boost::_bi::bind_t<>::operator()()
    @          0x2181172  boost::detail::function::void_function_obj_invoker0<>::invoke()
    @          0x20fba57  boost::function0<>::operator()()
    @          0x26cb779  impala::Thread::SuperviseThread()
    @          0x26d3716  boost::_bi::list5<>::operator()<>()
    @          0x26d363a  boost::_bi::bind_t<>::operator()()
    @          0x26d35fb  boost::detail::thread_data<>::run()
    @          0x3eb7ae1  thread_proxy
    @     0x7fc9443456b9  start_thread
    @     0x7fc940e334dc  clone
I0901 15:41:14.739985 25597 impala-hs2-server.cc:405] Opened session: 204a3f33cc8e28ea:d6a915ab96b26aa7 effective username: 
I0901 15:41:14.781677 25597 impala-hs2-server.cc:426] GetInfo(): request=TGetInfoReq {
  01: sessionHandle (struct) = TSessionHandle {
    01: sessionId (struct) = THandleIdentifier {
      01: guid (string) = "\xea(\x8e\xcc3?J \xa7j\xb2\x96\xab\x15\xa9\xd6",
      02: secret (string) = "\xf9\x11\xac\xf5wTB\xe8\xacN\r\x8e\xe3MJ\xa9",
    },   
  },
  02: infoType (i32) = 17,
}
I0901 15:41:14.785768 25597 impala-hs2-server.cc:426] GetInfo(): request=TGetInfoReq {
  01: sessionHandle (struct) = TSessionHandle {
    01: sessionId (struct) = THandleIdentifier {
      01: guid (string) = "\xea(\x8e\xcc3?J \xa7j\xb2\x96\xab\x15\xa9\xd6",
      02: secret (string) = "\xf9\x11\xac\xf5wTB\xe8\xacN\r\x8e\xe3MJ\xa9",
    },   
  },
  02: infoType (i32) = 18,
}
I0901 15:41:14.788753 25597 impala-hs2-server.cc:426] GetInfo(): request=TGetInfoReq {
  01: sessionHandle (struct) = TSessionHandle {
    01: sessionId (struct) = THandleIdentifier {
      01: guid (string) = "\xea(\x8e\xcc3?J \xa7j\xb2\x96\xab\x15\xa9\xd6",
      02: secret (string) = "\xf9\x11\xac\xf5wTB\xe8\xacN\r\x8e\xe3MJ\xa9",
    },   
  },
  02: infoType (i32) = 10006,
}

Maybe the hanging is due to this.

stakiar, do you know the background of the fetch.size setting of hive?

Issue Links

• is related to: IMPALA-12401 Support more info types for HS2 GetInfo() API