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
Following on from #2690, this is currently only affecting our compactor, however it could also affect other components depending on volume. Presumably the input blocks are valid, otherwise they would have failed to write as well. 4294952965 is suspiciously close to 4 GiB.
I think the first step here is to add recover logic to print out the offending input block IDs.
ok, let's try to get our facts in line to help diagnose this.
You see regular panics on compaction writes?
The blocks that are being read at the time of the compaction panic are fine or corrupt?
The panic is deterministic? i.e. it happens every time that Tempo attempts to compact these blocks?
I think the first step here is to add recover logic to print out the offending input block IDs.
Compactors only do one compaction job at a time. The offending block IDs would have been logged just before this panic.
4294952965 is suspiciously close to 4 GiB.
Good catch. I'm wondering if your compaction job is attempting to write a page that is larger than an internal max in parquet-go. Are you aware of anything exceptional about your data? Can you share your data so we can investigate?
This issue has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed after 15 days if there is no new activity.
Please apply keepalive label to exempt this Issue.
Describe the bug
Following on from #2690, this is currently only affecting our compactor, however it could also affect other components depending on volume. Presumably the input blocks are valid, otherwise they would have failed to write as well. 4294952965 is suspiciously close to 4 GiB.
I think the first step here is to add
recover
logic to print out the offending input block IDs.Environment:
latest
tag (cfb6e5429
)Additional Context
The text was updated successfully, but these errors were encountered: