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

Cron jobs halted and not logged to cron.job_run_details during demanding and long running job. #354

Open
Strijdhagen opened this issue Sep 3, 2024 · 0 comments

Comments

@Strijdhagen
Copy link

Strijdhagen commented Sep 3, 2024

Hi, I have a demanding job with high I/O (this might explain the issue) running every day at 23:05 (job 46)
I also have a job that runs every minute (job 17)
Once job 46 kicks off, everything will run as usual for about 15 minutes until 23:17, after which every job halts unti the demanding job finishes at 10:46. The first job in line imediatly kicks off then.

This is not the only long running job I have this issue with, all have in common that they are very demanding.

I understand this might be an issue of resources, but shouldn't there still be a log at the very least?
I'm running v1.6.0 on Supabase.

jobid runid job_pid database username command status return_message start_time end_time duration_seconds
17 169858 375047 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-03 00:12:00.016596+00 2024-09-03 00:12:00.159652+00 0.143056
17 169857 375014 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-03 00:11:02.466099+00 2024-09-03 00:11:02.635151+00 0.169052
17 169856 374928 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-03 00:10:46.421456+00 2024-09-03 00:11:02.448551+00 16.027095
3 169855 374927 postgres postgres SET statement_timeout = 1200000; REFRESH MATERIALIZED VIEW webjobs_xxx; succeeded REFRESH MATERIALIZED VIEW 2024-09-03 00:10:46.418529+00 2024-09-03 00:10:46.507085+00 0.088556
17 169854 365751 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:17:00.018151+00 2024-09-02 23:17:00.236743+00 0.218592
17 169853 365731 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:16:00.019839+00 2024-09-02 23:16:00.357227+00 0.337388
17 169852 365695 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:15:00.02412+00 2024-09-02 23:15:00.223141+00 0.199021
17 169851 365666 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:14:00.022749+00 2024-09-02 23:14:00.333433+00 0.310684
17 169850 365630 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:13:00.022326+00 2024-09-02 23:13:00.510576+00 0.488250
17 169849 365601 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:12:00.023159+00 2024-09-02 23:12:00.387185+00 0.364026
17 169848 365559 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:11:00.029286+00 2024-09-02 23:11:00.196384+00 0.167098
17 169847 365522 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:10:00.079774+00 2024-09-02 23:10:00.419515+00 0.339741
3 169846 365521 postgres postgres SET statement_timeout = 1200000; REFRESH MATERIALIZED VIEW webjobs_xxx; succeeded REFRESH MATERIALIZED VIEW 2024-09-02 23:10:00.068217+00 2024-09-02 23:12:10.416132+00 130.347915
17 169845 365476 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:09:00.020198+00 2024-09-02 23:09:00.393548+00 0.373350
17 169844 365436 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:08:00.032424+00 2024-09-02 23:08:00.462659+00 0.430235
17 169843 365396 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:07:00.020417+00 2024-09-02 23:07:00.232238+00 0.211821
17 169842 365341 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:06:00.025619+00 2024-09-02 23:06:00.211231+00 0.185612
17 169841 365291 postgres postgres SELECT update_matched_location(); succeeded 1 row 2024-09-02 23:05:00.026016+00 2024-09-02 23:05:00.15578+00 0.129764
27 169840 365290 postgres postgres SET statement_timeout = 1200000; REFRESH MATERIALIZED VIEW webjobs_xxx2; succeeded REFRESH MATERIALIZED VIEW 2024-09-02 23:05:00.024464+00 2024-09-02 23:06:54.567665+00 114.543201
46 169839 365289 postgres postgres SET statement_timeout = 72000000; REFRESH MATERIALIZED VIEW concurrently active_xxx; succeeded REFRESH MATERIALIZED VIEW 2024-09-02 23:05:00.020596+00 2024-09-03 00:10:46.285833+00 3946.265237
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant