[
https://issues.apache.org/jira/browse/AMBARI-23630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803423#comment-16803423
]
amarnath reddy pappu commented on AMBARI-23630:
-----------------------------------------------
[~rtrivedi12] Removing "-Dhive.log.dir={{hive_log_dir}} " entry from "Advanced
hive-env " metastore is resulting into logs file getting created at
/tmp/hive/hivemetaxxx.log path. further have reviewed bits of code at metastore
side and it appears like it is checking for some of these in conf files and if
not present then it prints this warning message.
For now i see this is not an issue at Ambari side and resolving the BUG - feel
free to re-open if there is any.
> Remove hive.log.dir from start scripts for metastore
> ----------------------------------------------------
>
> Key: AMBARI-23630
> URL: https://issues.apache.org/jira/browse/AMBARI-23630
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.0
> Reporter: Riju Trivedi
> Assignee: amarnath reddy pappu
> Priority: Major
>
> Remove hive.log.dir conf from ambari start scripts for metastore to avoid
> warnings in hive metastore logs.
> WARN [pool-7-thread-200]: conf.HiveConf
> ([HiveConf.java:initialize(3081)|http://hiveconf.javainitialize%283081%29/])
> - HiveConf of name hive.log.file does not exist
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
