pg_cron icon indicating copy to clipboard operation
pg_cron copied to clipboard

startup timeout after a certain amount of simultaneous jobs

Open elkejava opened this issue 2 years ago • 4 comments

I have some services which can be scheduled in pg_cron at the same time to be executed in a queue. The function runs a shell script which does some file copy operations on fileservers; the amount of data can be up to some GB and thus take a while. Until now (over two years), this setting worked fine also when there were big amounts of data and thus the next job in the queue starting with a very long delay (once there were about 40 minutes). Yersterday, I had first time 36 simultaneous jobs, four of them failed with "startup timeout" message, they started about 5 minutes later. I recently upgraded pg_cron to postgresql-12-cron 1.5.2-1.pgdg110+1 (debian bullseye). Can I get an information about the conditions of this startup timeout? Can I influence it? Thank you in advance for an explanation, Best, Elke

elkejava avatar Aug 02 '23 07:08 elkejava

It's a 10 second timeout, currently hard coded.

If cron.use_background_workers is enabled, it typically means max_worker_processes is exhausted. If cron.use_background_workers is disabled, it typically means it took more than 10 seconds to connect to localhost (server is overloaded maybe)

marcocitus avatar Sep 01 '23 14:09 marcocitus

Thank you, dear Marco. I have no setting cron.use_background_workers in my postgresql.conf, so how can I know if it es enabled or disabled? Best, Elke

Von: Marco Slot @.> Gesendet: Freitag, 1. September 2023 16:37 An: citusdata/pg_cron @.> Cc: Elke Hofmann @.>; Author @.> Betreff: Re: [citusdata/pg_cron] startup timeout after a certain amount of simultaneous jobs (Issue #282)

It's a 10 second timeout, currently hard coded.

If cron.use_background_workers is enabled, it typically means max_worker_processes is exhausted. If cron.use_background_workers is disabled, it typically means it took more than 10 seconds to connect to localhost (server is overloaded maybe)

Reply to this email directly, view it on GitHubhttps://github.com/citusdata/pg_cron/issues/282#issuecomment-1702856457, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4P2YLBRU6RY2AFXE7U5WLXYHXIDANCNFSM6AAAAAA3A2GEBM. You are receiving this because you authored the thread.Message ID: @.@.>>

elkejava avatar Sep 01 '23 15:09 elkejava

I have no setting cron.use_background_workers in my postgresql.conf, so how can I know if it es enabled or disabled?

it's disabled by default

marcocitus avatar Sep 08 '23 11:09 marcocitus

Thanks!

Von: Marco Slot @.> Gesendet: Freitag, 8. September 2023 13:32 An: citusdata/pg_cron @.> Cc: Elke Hofmann @.>; Author @.> Betreff: Re: [citusdata/pg_cron] startup timeout after a certain amount of simultaneous jobs (Issue #282)

I have no setting cron.use_background_workers in my postgresql.conf, so how can I know if it es enabled or disabled?

it's disabled by default

Reply to this email directly, view it on GitHubhttps://github.com/citusdata/pg_cron/issues/282#issuecomment-1711523211, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM4P2YNVPR727T5RZJDD3WTXZL64DANCNFSM6AAAAAA3A2GEBM. You are receiving this because you authored the thread.Message ID: @.@.>>

elkejava avatar Sep 08 '23 13:09 elkejava