HeartSaVioR edited a comment on issue #1286: URL: https://github.com/apache/iceberg/issues/1286#issuecomment-668021708
This is pretty much similar with what I posted in dev@ mailing list. https://lists.apache.org/thread.html/rf6c800ee3ea580a6c4dce377c292e9bc47a74ff5b27ccb79323e6426%40%3Cdev.iceberg.apache.org%3E There's a reasonable answer from @rdblue so you'd like to read through it. https://lists.apache.org/thread.html/r6d321b83baebe33e07f1632b176316aeb354c5a4f0d6397f056460ba%40%3Cdev.iceberg.apache.org%3E And the answer was similar with @openinx provided, 10s is a high rate on Iceberg, so you might want to have a longer interval, or implement your own logic on metadata R/W which accelerates the metadata write. Btw, I'd agree that there might be another valid idea to "prioritize" the commit and give "prioritized commit" change to retry couple of times without losing lock. (The problem here is that it's only available on Hive catalog.) We may want to see maintenance operations to be prioritized and succeed whenever possible, or exactly opposite. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
