Tempo compactor failures

We have set up a small Tempo cluster (three nodes in scalable-single-binary mode), and it’s running mostly fine.
However, we are getting compactor failures almost every compaction cycle):

googleapi: Error 404: No such object: /single-tenant/<block_id>/meta.json

The error message is sometimes slightly different:

  • failed to mark block compacted during retention

  • unable to mark block compacted

  • failed to clear compacted block during retention

but the inner error is always the above

Based on what we can find about these errors, it would appear that the compactor ring is not formed.
However, the ring status page looks fine (all three nodes show as active).

We use Consul as a kv store, not Grafana’s memberlist and GCS as block storage, otherwise our setup should be fairly default.

Any help is appreciated

It turned out we were advertising the wrong IP in the ring, see Compactor failures · Issue #4091 · grafana/tempo · GitHub

@rickvanhoef Hi Rick, I encountered the same issue, but the link you attached couldn’t open. Could you please provide some detailed messages? Thanks!

"level=error ts=2024-10-14T11:55:02.582180654Z caller=retention.go:71 msg="failed to mark block compacted during retention" blockID=xxxx tenantID=xxxx err="error copying obj meta to compacted obj meta: The specified key does not exist."