The ullimit should be in log not out (IMHO). That's the file you look at for
normal operations.
Can we log it to both places?
-- Lars
From: Stack <[email protected]>
To: Hbase-User <[email protected]>
Sent: Friday, October 10, 2014 10:36 PM
Subject: Re: log: ulimit output location
On Fri, Oct 10, 2014 at 6:45 PM, Stanley Shi <[email protected]> wrote:
> Hi users,
>
> I found that currently the hbase daemon will send the ulimit output to .log
> file;
> To my understanding:
> 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".
>
> So I was wondering why we put the ulimit output to .log file, why not to
> the .out file?
>
We've been doing it this way since near inception writing all we can to the
one log. IIRC, it was thought it just easier having one log carry all
needed to debug an install.
Anyone care if we change to align with how hdfs/yarn store environment
info, to .out rather than .log?
St.Ack
> BTW: for hadoop hdfs/yarn daemons, the ulimit information is printed to the
> .out file;
>
> --
> Regards,
> *Stanley Shi,*
>
