[
https://issues.apache.org/jira/browse/HIVE-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naveen Gangam updated HIVE-14672:
---------------------------------
Attachment: HIVE-14672.patch
The startup message will now look like
{code}
2016-08-30 15:27:47: Starting HiveServer2
2016-08-30 16:02:12: Starting HiveServer2
{code}
> Add timestamps to startup message in hive scripts.
> --------------------------------------------------
>
> Key: HIVE-14672
> URL: https://issues.apache.org/jira/browse/HIVE-14672
> Project: Hive
> Issue Type: Improvement
> Components: Hive
> Affects Versions: 2.0.0
> Reporter: Naveen Gangam
> Assignee: Naveen Gangam
> Priority: Minor
> Attachments: HIVE-14672.patch
>
>
> if hive services are started as background processes (most certainly the
> case) with output from stdout and stderr redirected to a file, certain fatal
> errors, like OutOfMemoryErrors, are printed to stderr. Such errors often do
> not have a timestamp associated with it. So overtime, after multiple restarts
> of the hive processes, the stdout/err redirect log looks like this
> {code}
> Starting Hive Metastore Server
> Starting Hive Metastore Server
> Exception in thread "main" java.lang.OutOfMemoryError: Requested array size
> exceeds VM limit
> Starting Hive Metastore Server
> {code}
> It would be useful to have a timestamp associated with the "Starting Hive
> Metastore Server" message to help debug when such errors may have occurred so
> we could look in the corresponding logs to help narrow down the issue.
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
