You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
run compaction/retention cycles without error
Environment:
aks v1.25.11
Additional Context
/ # df -hi /mnt
Filesystem Inodes Used Available Use% Mounted on
overlay 24.6M 2.2M 22.4M 9% /
Everything seems fine on PVC (yes base pvc since its just POC for Beyla/tempo deploy on development cluster), But as i said i cannot find anything wrong with PVC in terms of size and so on. But the block in WAL are failing the tempo.
Is this in work ? Do i have something wrong ?
My values.yaml for tempo are just basic
retention: 12h
persistence:
enabled: true
storageClassName: default
enableStatefulSetAutoDeletePVC: true
accessModes:
- ReadWriteOnce
size: 20Gi
changed only retention when i tried to solve it in the start, but it doesnt matter since issue is somewhere else.
Which version of tempo doesnt have this issue ? Is it in work ?...
Thx
The text was updated successfully, but these errors were encountered:
Describe the bug
error iterating input blocks: error iterating through block
To Reproduce
I just run https://github.com/grafana/helm-charts/blob/main/charts/tempo/values.yaml version 1.18.1 / app 2.7.0
Expected behavior
run compaction/retention cycles without error
Environment:
aks v1.25.11
Additional Context
/ # df -hi /mnt
Filesystem Inodes Used Available Use% Mounted on
overlay 24.6M 2.2M 22.4M 9% /
Everything seems fine on PVC (yes base pvc since its just POC for Beyla/tempo deploy on development cluster), But as i said i cannot find anything wrong with PVC in terms of size and so on. But the block in WAL are failing the tempo.
Is this in work ? Do i have something wrong ?
My values.yaml for tempo are just basic
retention: 12h
persistence:
enabled: true
storageClassName: default
enableStatefulSetAutoDeletePVC: true
accessModes:
- ReadWriteOnce
size: 20Gi
changed only retention when i tried to solve it in the start, but it doesnt matter since issue is somewhere else.
Which version of tempo doesnt have this issue ? Is it in work ?...
Thx
The text was updated successfully, but these errors were encountered: