osscm opened a new issue, #10335: URL: https://github.com/apache/iceberg/issues/10335
### Feature Request / Improvement Right now there is only one static Thread Pool, which Iceberg library uses internally. It picks a number based on the num of cores (https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/SystemConfigs.java#L42) From the engines like Trino and Spark, there is no way to control this. Users uses Trino to access multiple catalogs, so it becomes much more important from Trino to have this support. The, other problem with this approach is, that Engines using Iceberg will not have any control and trace of memory used by these Threads, and can it be directly proportional to the threads used. When Trino is running many concurrent queries, this can unearth a unstable Coordinator. https://github.com/apache/iceberg/blob/a78aa2dbdb98634f26066c457cc1aef93166be9f/core/src/main/java/org/apache/iceberg/util/ThreadPools.java#L41 related issues: https://github.com/trinodb/trino/issues/11920 https://github.com/trinodb/trino/issues/11708 ### Query engine None -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
