adiranjan25 commented on issue #18797: URL: https://github.com/apache/iceberg/issues/18797#issuecomment-6702537979
Hi @swapna267 , I'd like to take ownership of investigating and preparing a fix for this issue, if no one is already actively working on it. The reported race condition in `JdbcLockFactory.initializeLockTables()` appears to occur when multiple Flink maintenance operators concurrently check for the lock table's existence and attempt to create it. My proposed approach is to: 1. Add regression coverage for concurrent lock-table initialization. 2. Handle the table-already-exists race safely by verifying the table's existence after a conflicting creation attempt. 3. Preserve proper exception handling for genuine JDBC connection failures and other SQL errors. 4. Run the relevant Flink maintenance tests before submitting a PR. I'm planning to work on this shortly and would be happy to submit a focused PR referencing #18797. @maintainers, please let me know if there is a preferred approach or if someone is already working on a fix. I'd appreciate being assigned to this issue if appropriate, to help avoid duplicate efforts. Thanks! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
