[
https://issues.apache.org/jira/browse/HIVE-19886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526934#comment-16526934
]
Jaume M commented on HIVE-19886:
--------------------------------
[~kgyrtkirk] the choice of solutions are:
* Some initial logs would be sent to a different file until the reconfiguration
is done. These are the ones (since the Configuration object is created before
the reconfiguration happens):
{code}
2018-06-18T16:39:17,109 INFO [main] conf.MetastoreConf: Found configuration
file file:/hadoop-3.1.0/etc/hadoop/hive-site.xml
2018-06-18T16:39:17,364 INFO [main] conf.MetastoreConf: Unable to find config
file hivemetastore-site.xml
2018-06-18T16:39:17,364 INFO [main] conf.MetastoreConf: Found configuration
file null
2018-06-18T16:39:17,365 INFO [main] conf.MetastoreConf: Unable to find config
file metastore-site.xml
2018-06-18T16:39:17,365 INFO [main] conf.MetastoreConf: Found configuration
file null
{code}
* Warn in both files that a split is happening. Although I would do this as
well if we went with the first solution.
* Raise an exception
> 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
> Assignee: Jaume M
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-19886.2.patch, HIVE-19886.2.patch, HIVE-19886.patch
>
>
> 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)
