Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task with cron runs an hour later the first time #20353

Open
jcarranzar opened this issue Dec 16, 2020 · 3 comments
Open

Task with cron runs an hour later the first time #20353

jcarranzar opened this issue Dec 16, 2020 · 3 comments
Labels
area/tasks area/2.x OSS 2.0 related issues and PRs

Comments

@jcarranzar
Copy link

jcarranzar commented Dec 16, 2020

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

  1. Create task with cron at 15:00 (system time) -> for example: option task = {name: "CalculosT1", cron: "0 15 * * *", offset: 15m}

Expected behavior:
This task should be executed EVERY TIME at 15:00 (system time), in my case 14:00 UTC

Actual behavior:
First time after save or after reload docker container, the task runs 1 hour after, at 16 (system time)/ 15:00 UTC, it seems like dont get the cron correctly. Then, the other times it runs at 15:00 (system time)

Environment info:

  • System info: Linux 4.19.104-microsoft-standard x86_64
  • InfluxDB version: InfluxDB 2.0.3 (git: fe04d34) build_date: 2020-12-15T01:00:16Z
  • Other relevant environment details: Docker version 3.0.0 (50684)

Config:

Logs:

Performance:

@danxmoran danxmoran added area/2.x OSS 2.0 related issues and PRs area/tasks labels Dec 22, 2020
@jcarranzar
Copy link
Author

Hi there! It has been about 2 months and I would like to know if you have managed to replicate my issue or if it really is a bug or not. Thanks!

@danxmoran
Copy link
Contributor

danxmoran commented Jul 19, 2021

@wbaker85 and I are now both seeing this in this test when running locally on our Macs. The problem doesn't reproduce in CI.

EDIT: Might have spoken too soon. We do see an off-by-one failure but it's not on the 1st task run; it's when the task's schedule crosses over a daylight-savings-time boundary.

@jcarranzar
Copy link
Author

@danxmoran You have managed to find another clue of the bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/tasks area/2.x OSS 2.0 related issues and PRs
Projects
None yet
Development

No branches or pull requests

2 participants