Hi @csguna   Thank you for the reply.    Hive version is 1.1 and the cluster is managed by Cloudera manager.   For both HS2 hosts, the property is set to below values: hive.server2.logging.operation.enabled=true hive.server2.logging.operation.log.location=/var/log/hive/operation_logs hive.server2.logging.operation.verbose=undefined hive.server2.logging.operation.level=execution   But one HS2 is generating console logs for the jobs execution and the other one is not generating.   I have tried setting below value and retried, but no luck. hive.server2.logging.operation.verbose=true       ... View more

When I tried with --ldap_password_cmd="echo 'PASSWORD'" , getting below error.   Starting Impala Shell using LDAP-based authentication Error connecting: TTransportException, TSocket read 0 bytes *********************************************************************************** Welcome to the Impala shell. Copyright (c) 2015 Cloudera, Inc. All rights reserved. (Impala Shell v2.6.0-cdh5.8.2 (f25aa5b) built on Sun Sep 11 11:36:30 PDT 2016) Press TAB twice to see a list of available commands. *********************************************************************************** \nLDAP authentication is enabled, but the connection to Impala is not secured by TLS. ALL PASSWORDS WILL BE SENT IN THE CLEAR TO IMPALA. [Not connected] > ... View more

Thank you @HenryR for your reply!   I have tried this option, but it is not accepting.  $ impala-shell -i impala-host:21000 -l -u usernam --ldap_password_cmd="PASSWORD" --auth_creds_ok_in_clear Starting Impala Shell using LDAP-based authentication Error retrieving LDAP password (command was: 'PASSWORD', exception was: '[Errno 2] No such file or directory') ... View more

For both HS2 servers, env variable hive.session.silent is set to false already. However I have tried to use --silent=false, but no luck. ... View more

All nodes are managed by CM and there is no difference in /etc/hive/conf/log4j.properties of both HS2 servers. ... View more

HS2-1(Console log is generating) ========================== hive.root.logger is not there in beeline env list, but still console log is generating in HS2-1 $ beeline --outputformat=tsv2 -u "jdbc:hive2://HS2-1:10000/default;" -n user -w ~/.pass -e 'set -v;' 2>/dev/null | grep root.logger system:hadoop.root.logger=INFO,console   Hive root logger is set to INFO,console in configuration file.  $ grep hive.root.logger /etc/hive/conf/log4j.properties log4j.rootLogger=${hive.root.logger} hive.root.logger=INFO,console   Console is generating when executing a query 0: jdbc:hive2://HS2-1😆 select count(*) from scecomm_account_console; INFO : Compiling command(queryId=hive_20170208092828_aae117b5-eb16-489d-ba16-69aa30311ea2): select count(*) from scecomm_account_console INFO : Semantic Analysis Completed INFO : Returning Hive schema: Schema(fieldSchemas:[FieldSchema(name:_c0, type:bigint, comment:null)], properties:null) INFO : Completed compiling command(queryId=hive_20170208092828_aae117b5-eb16-489d-ba16-69aa30311ea2); Time taken: 0.169 seconds INFO : Executing command(queryId=hive_20170208092828_aae117b5-eb16-489d-ba16-69aa30311ea2): select count(*) from scecomm_account_console INFO : Query ID = hive_20170208092828_aae117b5-eb16-489d-ba16-69aa30311ea2 INFO : Total jobs = 1 INFO : Launching Job 1 out of 1 INFO : Starting task [Stage-1:MAPRED] in serial mode INFO : Number of reduce tasks determined at compile time: 1 INFO : In order to change the average load for a reducer (in bytes): INFO : set hive.exec.reducers.bytes.per.reducer=<number> INFO : In order to limit the maximum number of reducers: INFO : set hive.exec.reducers.max=<number> INFO : In order to set a constant number of reducers: INFO : set mapreduce.job.reduces=<number> INFO : number of splits:37 INFO : Submitting tokens for job: job_1486088124499_3537 INFO : The url to track the job: http://RM:8088/proxy/application_1486088124499_3537/ INFO : Starting Job = job_1486088124499_3537, Tracking URL = http://RM:8088/proxy/application_1486088124499_3537/ INFO : Kill Command = /opt/cloudera/parcels/CDH-5.8.2-1.cdh5.8.2.p0.3/lib/hadoop/bin/hadoop job -kill job_1486088124499_3537 INFO : Hadoop job information for Stage-1: number of mappers: 37; number of reducers: 1 INFO : 2017-02-08 09:28:25,516 Stage-1 map = 0%, reduce = 0% INFO : 2017-02-08 09:28:35,814 Stage-1 map = 3%, reduce = 0%, Cumulative CPU 5.29 sec INFO : 2017-02-08 09:28:38,896 Stage-1 map = 14%, reduce = 0%, Cumulative CPU 26.95 sec INFO : 2017-02-08 09:28:44,021 Stage-1 map = 19%, reduce = 0%, Cumulative CPU 37.67 sec INFO : 2017-02-08 09:28:47,103 Stage-1 map = 24%, reduce = 0%, Cumulative CPU 49.0 sec INFO : 2017-02-08 09:28:48,126 Stage-1 map = 27%, reduce = 0%, Cumulative CPU 54.61 sec INFO : 2017-02-08 09:28:50,191 Stage-1 map = 30%, reduce = 0%, Cumulative CPU 59.83 sec INFO : 2017-02-08 09:28:52,247 Stage-1 map = 32%, reduce = 0%, Cumulative CPU 65.23 sec INFO : 2017-02-08 09:28:53,277 Stage-1 map = 35%, reduce = 0%, Cumulative CPU 70.57 sec INFO : 2017-02-08 09:28:56,359 Stage-1 map = 41%, reduce = 0%, Cumulative CPU 81.39 sec INFO : 2017-02-08 09:28:57,394 Stage-1 map = 43%, reduce = 0%, Cumulative CPU 87.06 sec INFO : 2017-02-08 09:28:59,443 Stage-1 map = 46%, reduce = 0%, Cumulative CPU 91.11 sec INFO : 2017-02-08 09:29:00,474 Stage-1 map = 49%, reduce = 0%, Cumulative CPU 96.6 sec INFO : 2017-02-08 09:29:03,554 Stage-1 map = 51%, reduce = 0%, Cumulative CPU 102.1 sec INFO : 2017-02-08 09:29:05,600 Stage-1 map = 54%, reduce = 0%, Cumulative CPU 107.42 sec INFO : 2017-02-08 09:29:06,632 Stage-1 map = 57%, reduce = 0%, Cumulative CPU 112.72 sec INFO : 2017-02-08 09:29:09,710 Stage-1 map = 62%, reduce = 0%, Cumulative CPU 123.61 sec INFO : 2017-02-08 09:29:14,840 Stage-1 map = 65%, reduce = 0%, Cumulative CPU 129.43 sec INFO : 2017-02-08 09:29:15,863 Stage-1 map = 70%, reduce = 0%, Cumulative CPU 141.22 sec INFO : 2017-02-08 09:29:18,935 Stage-1 map = 73%, reduce = 0%, Cumulative CPU 146.75 sec INFO : 2017-02-08 09:29:20,988 Stage-1 map = 76%, reduce = 0%, Cumulative CPU 152.25 sec INFO : 2017-02-08 09:29:22,016 Stage-1 map = 78%, reduce = 0%, Cumulative CPU 157.74 sec INFO : 2017-02-08 09:29:24,059 Stage-1 map = 81%, reduce = 0%, Cumulative CPU 163.44 sec INFO : 2017-02-08 09:29:25,079 Stage-1 map = 84%, reduce = 0%, Cumulative CPU 169.15 sec INFO : 2017-02-08 09:29:28,147 Stage-1 map = 86%, reduce = 0%, Cumulative CPU 174.86 sec INFO : 2017-02-08 09:29:29,170 Stage-1 map = 87%, reduce = 0%, Cumulative CPU 179.94 sec INFO : 2017-02-08 09:29:31,216 Stage-1 map = 92%, reduce = 0%, Cumulative CPU 185.99 sec INFO : 2017-02-08 09:29:32,240 Stage-1 map = 95%, reduce = 0%, Cumulative CPU 191.63 sec INFO : 2017-02-08 09:29:35,317 Stage-1 map = 95%, reduce = 32%, Cumulative CPU 192.51 sec INFO : 2017-02-08 09:29:36,348 Stage-1 map = 97%, reduce = 32%, Cumulative CPU 198.02 sec INFO : 2017-02-08 09:29:40,454 Stage-1 map = 100%, reduce = 32%, Cumulative CPU 204.04 sec INFO : 2017-02-08 09:29:41,487 Stage-1 map = 100%, reduce = 67%, Cumulative CPU 204.22 sec INFO : 2017-02-08 09:29:42,515 Stage-1 map = 100%, reduce = 100%, Cumulative CPU 206.68 sec INFO : MapReduce Total cumulative CPU time: 3 minutes 26 seconds 680 msec INFO : Ended Job = job_1486088124499_3537 INFO : MapReduce Jobs Launched: INFO : Stage-Stage-1: Map: 37 Reduce: 1 Cumulative CPU: 206.68 sec HDFS Read: 9856069385 HDFS Write: 9 SUCCESS INFO : Total MapReduce CPU Time Spent: 3 minutes 26 seconds 680 msec INFO : Completed executing command(queryId=hive_20170208092828_aae117b5-eb16-489d-ba16-69aa30311ea2); Time taken: 88.306 seconds INFO : OK _c0 54265941 1 row selected (88.51 seconds)         HS2-2(Console log is not generating) ================================= Same root.logger properties for HS2-2 also, but it is not showing console logs.   $ beeline --outputformat=tsv2 -u "jdbc:hive2://HS2-2:10000/default;" -n user -w ~/.pass -e 'set -v;' 2>/dev/null | grep root.logger system:hadoop.root.logger=INFO,console   Hive root logger is set to INFO,console in configuration file.  $ grep hive.root.logger /etc/hive/conf/log4j.properties log4j.rootLogger=${hive.root.logger} hive.root.logger=INFO,console     Console log is not generating while connecting to HS2-2 0: jdbc:hive2://HS2-2😆 select count(*) from scecomm_account_console; _c0 54265941   Tried to set hive.root.logger manually, but still no luck.   0: jdbc:hive2://HS2-2😆 set hive.root.logger=INFO,console; No rows affected (0.002 seconds) 0: jdbc:hive2://HS2-2😆 set hive.root.logger; set hive.root.logger=INFO,console 1 row selected (0.005 seconds) 0: jdbc:hive2://HS2-2😆 select count(*) from scecomm_account_console; _c0 54265941 1 row selected (143.116 seconds)           ... View more

Yes @mbigelow. I am getting these logs in another HS2 server, but not in one of the HS2.        ... View more

Thank you @mbigelow for your reply!   Setting the consoletype variable didn't helped here, still I am not getting console logs. It is just showing the output of the query without any console logs. Please find the below.   0: jdbc:hive2://HS2-node:> set CONSOLETYPE; set CONSOLETYPE=vt 1 row selected (0.072 seconds)   0: jdbc:hive2://HS2-node:> select count(*) from npevent; _c0 253427762 1 row selected (305.41 seconds) ... View more