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

schedule is not executed according to the schedule #639

Open
JuchangGit opened this issue Jul 31, 2024 · 7 comments
Open

schedule is not executed according to the schedule #639

JuchangGit opened this issue Jul 31, 2024 · 7 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@JuchangGit
Copy link

我的 schedule: "*/33 * * * *"
但是执行时间表是: 00:00:00 00:33:00 01:00:00 01:33:00 ...
这并不是每33分钟执行一次

@yohamta yohamta added bug Something isn't working good first issue Good for newcomers needs-investigation labels Jul 31, 2024
@codinggeeks06
Copy link

codinggeeks06 commented Aug 22, 2024

I have 15 dags scheduled at
schedule: 0 9 * * *
I checked the yaml. it is correct. but some of the dags did run at 9'o clock. and some of those didn't run.

@yohamta
Copy link
Collaborator

yohamta commented Aug 22, 2024

Could you please share the scheduler's log? Are the DAGs on NFS or local disk?

@ghansham
Copy link

ghansham commented Aug 22, 2024

The dags are on nfs. We can move them to local directory. Does nfs has something to do about it?

@JuchangGit
Copy link
Author

schedule: "*/30 * * * "
schedule: "
/20 * * * *"
我的都是没有问题的

schedule: "*/33 * * * *"
就有问题了,这样始终会每30分钟执行一次,而不是33分钟

@yohamta
Copy link
Collaborator

yohamta commented Aug 28, 2024

The file event watcher may not function properly when DAG files are stored on NFS, which can prevent the scheduler from automatically reloading updated DAG files. In such cases, you'd need to manually restart the scheduler process to ensure it picks up the latest DAG files and their scheduling configurations.
We've already implemented a polling mechanism as a workaround for NFS, instead of relying on file events. However, we're not entirely sure if this solution covers all scenarios.

For a more robust solution in future versions, I'm considering reading DAGs directly from a GitHub branch or some type of database. This approach should resolve these issues.

@JuchangGit
Copy link
Author

我用的不是nfs,我的问题不是没有调度起来,而是当调用频次不是整 十分钟 的时候 调度会近似到 整十分钟

@JuchangGit
Copy link
Author

我可能没有说明白,看看我的截图
image
image

正确的调度表应该是
1:33
2:03
2:36
3:09
3:42
...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants