You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Prasanth Jayachandran (JIRA)" <ji...@apache.org> on 2015/11/23 11:30:11 UTC

[jira] [Updated] (HIVE-12497) Remove HADOOP_CLIENT_OPTS from hive script

     [ https://issues.apache.org/jira/browse/HIVE-12497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanth Jayachandran updated HIVE-12497:
-----------------------------------------
    Attachment: HIVE-12497.1.patch

Removing HADOOP_CLIENT_OPTS, we will get errors like 
"ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console." during startup. This is because hadoop is still using old log4j1.x. This really does not matter as it is being thrown by "hadoop version" command. What really matters is hive saying successful initialization of logging like below
"Logging initialized using configuration in file:/work/configs/hive/pseudo-distributed/hive-log4j2.xml"

> Remove HADOOP_CLIENT_OPTS from hive script
> ------------------------------------------
>
>                 Key: HIVE-12497
>                 URL: https://issues.apache.org/jira/browse/HIVE-12497
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Logging
>    Affects Versions: 2.0.0
>            Reporter: Prasanth Jayachandran
>            Assignee: Prasanth Jayachandran
>             Fix For: 2.0.0
>
>         Attachments: HIVE-12497.1.patch
>
>
> HADOOP_CLIENT_OPTS added in HIVE-11304 to get around log4j error adds ~5 seconds delay to hive startup. 
> {code:title=with HADOOP_CLIENT_OPTS}
> time hive --version
> real	0m11.948s
> user	0m13.026s
> sys	0m3.979s
> {code}
> {code:title=without HADOOP_CLIENT_OPTS}
> time hive --version
> real	0m7.053s
> user	0m7.254s
> sys	0m3.589s
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)