search

mesos / chronos

Fault tolerant job scheduler for Mesos which handles dependencies and ISO8601 based schedules
http://mesos.github.io/chronos/
Apache License 2.0
4.39k stars 529 forks source link

Chronos UI doesn't support "scheduleTimeZone" when job is created. #813

Open alex-ren opened 7 years ago

alex-ren commented 7 years ago

I observed the following in Chronos v3.0.0.

The Chronos documentation says Chronos support "scheduleTimeZone", and it has high priority. I defined the job as the following. { "schedule": "R1/2017-03-11T17:25:00Z/PT12H", "scheduleTimeZone": "PST", "name": "samplejob", "epsilon": "PT15M", "command": "/bin/date; sleep 3; echo 'helloy'", "owner": "bob@vmware.com", "cpus": "0.2", "mem": "256", "async": false } I expected the job to start in five minutes. However the UI showed that the job is OVERDUE. But then I manually started the job. After the job succeeded, the UI showed that the next run is in 4 minutes. (The execution of the job took about 1 minute.)

Then I defined the job as the following. { "schedule": "R1/2017-03-11T17:25:00-08:00/PT12H", "name": "samplejob", "epsilon": "PT15M", "command": "/bin/date; sleep 3; echo 'helloy'", "owner": "bob@vmware.com", "cpus": "0.2", "mem": "256", "async": false } The UI showed that the job will start in 3 minutes. (Another one minute just passed for creating a new job.)

It seems that the UI is not handling the "scheduleTimeZone" correctly at the first time.

brndnmtthws commented 7 years ago

That's true, the UI doesn't handle timezones.