hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naveen Gangam (JIRA)" <>
Subject [jira] [Commented] (HIVE-16769) Possible hive service startup due to the existing file /tmp/stderr
Date Wed, 31 May 2017 21:04:04 GMT


Naveen Gangam commented on HIVE-16769:

The change makes sense to me. 
Re-directing output that is to be written to a process' STDERR into a file in /tmp can be
a problem for users at certain financial institutions. They are generally required to save
logs for an extended periods and defaulting to /tmp would not meet their requirements. Printing
it to the console allows them to redirect them to a more "permanent" location via process
managers/monitors that are use to start/stop hive services. Hope this makes sense. So +1 for

[~prasanth_j] and [~gopalv] Please do share your concerns if you have any.

> Possible hive service startup due to the existing file /tmp/stderr
> ------------------------------------------------------------------
>                 Key: HIVE-16769
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 2.0.0
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>         Attachments: HIVE-16769.1.patch
> HIVE-12497 prints the ignoring errors from hadoop version, hbase mapredcp and hadoop
jars to /tmp/$USER/stderr. 
> In some cases $USER is not set, then the file becomes /tmp/stderr.  If  such file preexists
with different permission, it will cause the service startup to fail.
> I just tried the script without outputting to stderr file, I don't see such error any
more {{"ERROR StatusLogger No log4j2 configuration file found. Using default configuration:
logging only errors to the console."}}.
> I think we can remove such redirect to avoid possible startup failure.

This message was sent by Atlassian JIRA

View raw message