Open edgarkz opened 6 days ago
Hi! How are you deploying Tempo, in distributed mode? Is it possible that the different blocks were being flushed by different ingesters? They are very different in size also (TotalObjects
and Size
). It seems that the config is not applied to the new ingesters
Hi Mario, 1# Indeed distributed mode, any reason ingesters ignore the config? There is no way only some picked the config since the chart itself restarts all the pods with new version upgrade and also i did some rolling restarts just to be on safe side.
2# all those rogue blocks have { ReplicationFactor:1}"
while those with dedicated column - ReplicationFactor:0}"
what does it mean the RF here?
Describe the bug Since latest tempo 2.6 setup and migration to vParquet4 - dedicated columns related outputs are unclear and i suspect they are not working well, some of blocks do have dedicated column output but others are not.
Below is my storage related configuration:
Tempo cli doesnt show anymore if those top used attributes are within dedicated column (they were shown for sure in tempo 2.5)
Compactor logs:
Environment:
Additional Context