Hi,
We are seeing tempodb_compaction_outstanding_blocks increasing continuously post reducing the compactor replica count from 3 to 1.
We faced this issue: #2560
Errors says: If multiple replicas are used, then they may be process same traces for compaction reutilizing in this error.
Article toomanyoutstandingblocks asking to increase compactor count, but we may face issue #2560 again.
Our Single Compactor Replica Utilization around 2.5GB and running smoothly in our Docker Swarm Cluster, while limits are below.
resources:
limits:
memory: 4096M
reservations:
memory: 256M
Current Tempo Version: 2.7.0
Checked: #4067 (comment) , on Single Replica, will it be beneficial to decrease [compaction_window: <duration>] to 30 mins in reducing tempodb_compaction_outstanding_blocks?
Few Queries:
-
How to manage/reduce
tempodb_compaction_outstanding_blockswithout compromising performance? -
Is
block_list_length&tempodb_compaction_outstanding_blockshas any relation between them? In our casesince few months block_list_lenghtstable at27kfor 90 days retention data, buttempodb_compaction_outstanding_blocksincreasing to44kfrom 30th July 2025 on 90 Days retention data.
