Use TimescaleTiered Storage

Troubleshooting

This section contains some ideas for troubleshooting common problems experienced with data tiering.

Slow tiering of chunks

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

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.

Keywords

tiered storagedata tieringtroubleshooting

Found an issue on this page?Report an issue or Edit this page in GitHub.

PreviousReplicas and forks with tiered dataNextHyperfunctions

Related Content

Tiered Storage
Save on storage costs by tiering older data to a low-cost bottomless object storage tier. Timescale Cloud tiered storage makes sure you cut costs while having data available for analytical queries
About the object storage tier
Learn how Timescale Cloud helps you save on storage costs. The Timescale Cloud tiered storage architecture includes a high-performance storage tier and a low-cost object storage tier built on Amazon s3
Querying Tiered Data
Tiering data to low-cost object storage does not mean that it can't be queried. Learn how Timescale Cloud lets you optimize storage while still being able to run analytical queries on the rarely used data
Manage tiering
Enable tiered storage for your data in Timescale Console. With automated data tiering policies, you get a set it and forget it tool to cut storage costs
Replicas and forks with tiered data
While having replicas of your Timescale Cloud service usually entails additional storage costs, tiering data to object storage means your replicas come for free. Learn how this works under the hood
Troubleshooting jobs
Suggestions for troubleshooting common problems in jobs