I'm afraid I don't know what the SLS is. Obviously it shouldn't matter if it
runs on the same node. I don't think hadoop code ever updates the system clock.
In fact it shouldn't even be run with the perms to do so.It depends on log4j
appenders whether they buffer and batch the messages before
Thanks for the diagrams tip! I will try it.
(SLS is the Scheduler Load Simulator
http://hadoop.apache.org/docs/r2.6.0/hadoop-sls/SchedulerLoadSimulator.html
)
Regards
Fabio
On 01/27/2015 11:04 PM, Ravi Prakash wrote:
I'm afraid I don't know what the SLS is. Obviously it shouldn't
matter if
Are you running NTP?
On Friday, January 23, 2015 12:42 AM, Fabio anyte...@gmail.com wrote:
Hi guys,
while analyzing SLS logs I noticed some unexpected behaviors, such as
resources requests sent before the AM container gets to a RUNNING state.
For this reason I started wondering how
Yes I am, does it make a difference? SLS runs on a single machine,
wrapping the RM and simulating the nodes, thus it should use just the
system time.
Or do you mean there is a chance it's updating the clock while the job
is running?
Regards
Fabio
On 01/26/2015 08:00 PM, Ravi Prakash wrote:
Hi guys,
while analyzing SLS logs I noticed some unexpected behaviors, such as
resources requests sent before the AM container gets to a RUNNING state.
For this reason I started wondering how reliable is the timestamp of the
log entries.
Does log4j run on an independent thread? If yes, could it
