Any larger use of log management will end up with servers in two different time zones. The ops team will inevitably set all machines to run with time zone UTC. After that, all of the logs will be in UTC.
On Mon, Jun 6, 2016 at 9:49 AM, Edwards, Jesse <[email protected]> wrote: > While I can't speak to Airflow's exact requirement. > > > For me the really clear reason is: > > > 1. All other timezones are based off UTC +/- some amount. Thus calculating > the time in any given timezone is trivial. > > 2. UTC does not have daylight savings! It really sucks and throws systems > out of whack when they think there are two 2AM hours on Time change =). > > > Jesse > > ________________________________ > From: Eric Johnson <[email protected]> > Sent: Monday, June 6, 2016 9:28:54 AM > To: [email protected] > Subject: UTC everywhere requirement > > Hi - > > I see that at the moment Airflow wants everything to be in UTC. > > Can those who understand this requirement speak a bit about where in the > code this dependency exists? I took a cursory glance through the code in a > brief attempt to understand the scope of this issue and it wasn't > immediately obvious where this was even assumed. I don't doubt it. Just > didn't spot it. > > I can certainly understand the need for all of airflow to run in the same > time zone. But I find it odd that it really needs everything to be UTC and > only UTC. > > Eric > -- Lance Norskog [email protected] Redwood City, CA
