Unset trace retention period prevents chunk compression

[tilpner]

After migrating promscale to a new server, I must have forgotten to set the trace retention period, but everything appeared to be working fine. I've then upgraded promscale to 0.8 and 0.9, and sometime inbetween the maintenance jobs must have stopped working.

When calling the maintenance function manually, it errored because the trace retention period was unset. This prevents chunks from being compressed, and rapidly fills up available disk space.

I've set the trace retention period now, and the maintenance job is slowly freeing up space by compressing old chunks, so I can't provide the exact error anymore.

[VineethReddy02]

@tilpner thanks for reporting this issue, So the issue you reported is on the upgrade from 0.8 to 0.9`? And setting the retention period explicitly fixed the maintenance jobs?

Am I correct with the understanding of your issue?

[tilpner]

The issue occured after my upgrade from 0.8 to 0.9, but it could also affect later versions if no change has been made to handle an unset retention period.

Setting the retention period allowed the maintenance jobs to execute at all, instead of erroring. However, I'm now experiencing more issues with the maintenance jobs, where they take up many hours of CPU usage every day for an unknown reason. I don't know if that's an unrelated issue.