-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive memory usage in Iceberg connector since version 468 #25077
Comments
@vburenin Can you confirm the behavior on 467, 468 and 469? We want to know the exact version we introduced the issue. |
Trino 468 has this issue. |
467 does not. So, Trino 468 it is where the issue starts to happen. And it seems like it is iteratively got worse at 470. |
The notable change in Trino 468 is Iceberg Upgrade to 1.7.1 from 1.7.0 |
Downgraded Iceberg to 1.7.0 in Trino 470. The problem didn't go away. |
I have set iceberg.bucket-execution to false and the problem seems to be gone. |
cc: @dain @raunaqmorarka |
I just recently did an upgrade from Trino 466 to 470 and operation like 'show columns from' or 'show create table' for Iceberg table started to fail miserably.
The table itself has just several top level fields and one of the fields is a deeply nested data structure with around 7k projected fields.
After digging deeper, I discovered an excessive memory usage in Iceberg module:
It appears there is an array with 7k record where each record is 2.5MB on average.
I can't share a data structure details due to the sensitivity of the content, however, I hope there is something obvious.
This is a critical bug for us as it makes Trino cluster fully unusable.
The text was updated successfully, but these errors were encountered: