[ https://issues.apache.org/jira/browse/HIVE-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511684#comment-16511684 ]
Prasanth Jayachandran commented on HIVE-19886: ---------------------------------------------- The workaround for now is to run the hive commands like {code:java} HADOOP_CLIENT_OPTS="$HADOOP_CLIENT_OPTS -Dhive.log.dir=/tmp/hive -Dhive.log.file=hiveserver2.log" hive --service hiveserver2{code} and not use --hiveconf hive.log.file > Logs may be directed to 2 files if --hiveconf hive.log.file is used > ------------------------------------------------------------------- > > Key: HIVE-19886 > URL: https://issues.apache.org/jira/browse/HIVE-19886 > Project: Hive > Issue Type: Bug > Components: Logging > Affects Versions: 3.1.0, 4.0.0 > Reporter: Prasanth Jayachandran > Priority: Major > > hive launch script explicitly specific log4j2 configuration file to use. The > main() methods in HiveServer2 and HiveMetastore reconfigures the logger based > on user input via --hiveconf hive.log.file. This may cause logs to end up in > 2 different files. Initial logs goes to the file specified in > hive-log4j2.properties and after logger reconfiguration the rest of the logs > goes to the file specified via --hiveconf hive.log.file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)