pvary commented on issue #7034: URL: https://github.com/apache/iceberg/issues/7034#issuecomment-1512432038
> It sounds like this should be a threadpool that is owned by the catalog, not a thread per table. > > @pvary, can you confirm whether this is working in 1.2 and what we can do to avoid needing to manage resources per table? We need different threads for heartbeating different Hive locks. It was technically OK when we bound it to the HiveTableOperation, as there were no concurrent commits for a single operation, but putting it on the Catalog level could cause noisy neighbors problem when multiple tables are using the same thread pool. The issue should not be present after #6648, as it binds the heartbeat thread to the Lock itself, which is the correct place for it. -- 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 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
