Open mkindahl opened 1 year ago
Other
Background worker
If the scheduler exits for any reason, no more workers will be scheduled since the scheduler do not restart automatically.
This is because the scheduler is started with BGW_NEVER_RESTART as restart time.
BGW_NEVER_RESTART
2.9.0
14.3
Ubuntu 22.04 x86_64
Source
Not applicable
No response
Wait for the scheduler to exit with an error. This can be triggered creating duplicate job entries in the bgw_job table, for example.
There turned out to be issue with this over time since the slots are not released and new schedulers are started by the launcher.
What type of bug is this?
Other
What subsystems and features are affected?
Background worker
What happened?
If the scheduler exits for any reason, no more workers will be scheduled since the scheduler do not restart automatically.
This is because the scheduler is started with
BGW_NEVER_RESTART
as restart time.TimescaleDB version affected
2.9.0
PostgreSQL version used
14.3
What operating system did you use?
Ubuntu 22.04 x86_64
What installation method did you use?
Source
What platform did you run on?
Not applicable
Relevant log output and stack trace
No response
How can we reproduce the bug?
Wait for the scheduler to exit with an error. This can be triggered creating duplicate job entries in the bgw_job table, for example.