David Robinson created AURORA-275:
-------------------------------------
Summary: Scheduler logs do not have a consistent format
Key: AURORA-275
URL: https://issues.apache.org/jira/browse/AURORA-275
Project: Aurora
Issue Type: Task
Components: Scheduler
Reporter: David Robinson
Priority: Minor
The logs produced by the scheduler do not have a consistent format. The time
field sometimes shows milliseconds and sometimes microseconds. The PID field
sometimes shows THREAD123456 and sometimes 123456. The 'where' field (line of
source code) is also inconsistent. I suspect the inconsistencies are due to the
C++ components (mesos scheduler driver) using one format and the Java
components (scheduler) using another. It would be great if a single format were
used -- it would make parsing logs much simpler (the year being present in the
logs would also help)!
{noformat:title=snippet from scheduler log}
I0318 00:01:04.990661 48928 sched.cpp:619] Scheduler::statusUpdate took
3.007863033secs
I0318 00:01:04.990 THREAD23
com.twitter.common.util.StateMachine$Builder$1.execute:
1395100861984-mesos-test-slave-recovery-spinner-196-75dece23-24b9-4e5d-8bb4-4352bb545133
state machine transition PENDING -> ASSIGNED
I0318 00:01:04.990767 48928 sched.cpp:576] Ignoring task status update message
because the driver is aborted!
I0318 00:01:04.990 THREAD23
org.apache.aurora.scheduler.state.TaskStateMachine.addFollowup: Adding work
command SAVE_STATE for
1395100861984-mesos-test-slave-recovery-spinner-196-75dece23-24b9-4e5d-8bb4-4352bb545133
I0318 00:01:04.990900 48928 sched.cpp:484] Ignoring resource offers message
because the driver is aborted!
I0318 00:01:04.990957 48928 sched.cpp:576] Ignoring task status update message
because the driver is aborted!
{noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
