Thanos Compact stops operation permanently even after temporary issues

Summary

Thanos Compact stops its operation unexpected when there are issues, like connection loss to object storage. The problem is that it doesn't resume itself after that, any more. That's already discussed here: https://github.com/thanos-io/thanos/issues/2887#issuecomment-679946980.

Use Cases

Proposal

Introduce the flag --no-debug.halt-on-error to the Thanos Compact cmdline. (After some testing it seems --debug.halt-on-error doesn't do the trick.)

Specification

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this section are to be interpreted as described in RFC 2119.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information