Troubleshooting

Your scheduled jobs might stop running for various reasons. On self-hosted TimescaleDB, you can fix this by restarting background workers:

TimescaleDB >= 2.12

TimescaleDB < 2.12

SELECT _timescaledb_functions.start_background_workers();

Copy

On Timescale and Managed Service for TimescaleDB, restart background workers by doing one of the following:

• Run SELECT timescaledb_pre_restore(), followed by SELECT timescaledb_post_restore().
• Power the service off and on again. This might cause a downtime of a few minutes while the service restores from backup and replays the write-ahead log.

Chunks are tiered asynchronously. Chunks are selected to be tiered to the object storage tier one at a time ordered by their enqueue time.

To see the chunks waiting to be tiered query the timescaledb_osm.chunks_queued_for_tiering view

select count(*) from timescaledb_osm.chunks_queued_for_tiering

Copy

Processing all the chunks in the queue may take considerable time if a large quantity of data is being migrated to the object storage tier.