Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
Impala 2.5.0
Description
We recently upgrade to Cloudera 5.4 from 5.7 which is now running impala 2.5.0. We had YARN integration turned on prior to the upgrade and it was running without issue.
After the upgrade, it doesn't appear that we are able to run any queries with it turned on. When attempting to run a query the shell immediately disconnects with the following error:
Error communicating with impalad: TSocket read 0 bytes
And in the logs we get a notice of a segfault:
/var/log/impala/impala.INFO
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x0000000000a86ab0, pid=6357, tid=140428910843648 # # JRE version: Java(TM) SE Runtime Environment (7.0_67-b01) (build 1.7.0_67-b01) # Java VM: Java HotSpot(TM) 64-Bit Server VM (24.65-b04 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [impalad+0x686ab0] impala::GetEffectiveUser(impala::TSessionState const&)+0x0 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /var/run/cloudera-scm-agent/process/2678-impala-IMPALAD/hs_err_pid6357.log