aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhuvan Arumugam (JIRA)" <>
Subject [jira] [Created] (AURORA-444) same scheduler log entries in multiple timezones
Date Fri, 16 May 2014 23:06:44 GMT
Bhuvan Arumugam created AURORA-444:

             Summary: same scheduler log entries in multiple timezones
                 Key: AURORA-444
             Project: Aurora
          Issue Type: Bug
          Components: Scheduler
    Affects Versions: 0.6.0
            Reporter: Bhuvan Arumugam

aurora and mesos library used within scheudler seem to log in different timezones.

All hosts in the cluster are in same timezone, PDT. The mesos library(?) replica.cpp, leveldb.cpp
seem to log in this timezone; whereas scheduler classes like com.twitter.common.util.StateMachine$Builder$1.execute,
seem to log in UTC timezone. I think both should honor system timezone, or is it configurable?

I0516 00:02:56.176036  2740 replica.cpp:671] Persisted action at 33049
I0516 00:02:56.176431  2736 replica.cpp:650] Replica received learned notice for position
I0516 00:02:56.178455  2736 leveldb.cpp:337] Persisting action (2029 bytes) to leveldb took
I0516 00:02:56.178517  2736 replica.cpp:671] Persisted action at 33049
I0516 00:02:56.178534  2736 replica.cpp:656] Replica learned APPEND action at position 33049
I0516 07:02:56.181 THREAD33 com.twitter.common.util.StateMachine$Builder$1.execute: 1400223476167-anindya_sinha-prod-memcached-server-0-693d6e04-7297-46f6-ac79-5753113c466a
state machine transition PENDING -> ASSIGNED
I0516 07:02:56.181 THREAD33 org.apache.aurora.scheduler.state.TaskStateMachine.addFollowup:
Adding work command SAVE_STATE for 1400223476167-anindya_sinha-prod-memcached-server-0-693d6e04-7297-46f6-ac79-5753113c466a
I0516 07:02:56.183 THREAD33 org.apache.aurora.scheduler.state.TaskAssigner$TaskAssignerImpl.assign:
Offer on slave (id value: "20140512-151150-360689681-5050-7152-9"
) is being assigned task for 1400223476167-anindya_sinha-prod-memcached-server-0-693d6e04-7297-46f6-ac79-5753113c466a.
I0516 00:02:56.185482  3137 log.cpp:849] Attempting to append 2181 bytes to the log
I0516 00:02:56.185683  2726 coordinator.cpp:335] Coordinator attempting to write APPEND action
at position 33050
I0516 00:02:56.186553  2732 replica.cpp:515] Replica received write request for position 33050
I0516 00:02:56.188377  2732 leveldb.cpp:337] Persisting action (2202 bytes) to leveldb took
I0516 00:02:56.188439  2732 replica.cpp:671] Persisted action at 33050

This message was sent by Atlassian JIRA

View raw message