[
https://issues.apache.org/jira/browse/HBASE-12211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14166143#comment-14166143
]
stanley shi commented on HBASE-12211:
-------------------------------------
Hi [~stack], we should not put everything in to one single file to make it
contains everything.
The .out file is used to store stdout and stderr (in case user misconfigured
log4j, all hbase logs will goto this file).
The .log file is meant to store only the log4j outputs from the hbase codes.
This .out and .log files together makes the "hbase log".
Customer need to let the supporter to know the ulimit value, but not need it in
the ".log" file.
> hbase-daemon.sh should direct the ulimit output to logout instead of loglog
> ---------------------------------------------------------------------------
>
> Key: HBASE-12211
> URL: https://issues.apache.org/jira/browse/HBASE-12211
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0
> Reporter: stanley shi
> Priority: Minor
>
> In the hbase-daemon.sh file line 199, it has the content:
> {quote}echo "`ulimit -a`" >> $loglog 2>&1{quote}
> The variable loglog is defined as:
> {quote}
> logout=$HBASE_LOG_DIR/$HBASE_LOG_PREFIX.out
> loggc=$HBASE_LOG_DIR/$HBASE_LOG_PREFIX.gc
> loglog="${HBASE_LOG_DIR}/${HBASE_LOGFILE}"
> {quote}
> For my understanding, this information should be printed to the "logout"
> variable; we should not mix this "ulimit" information with the actual log
> printed by hbase java program.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
