KnightChess opened a new pull request, #10412: URL: https://github.com/apache/hudi/pull/10412
config: occ open use FileSystemBasedLock mdt is open in write defualt there has three job, jobA, jobB, jobC, these three jobs are running at the same time. jobA get lock success, jobB has been trying to get lock, jobC also try to get lock. jobB failed because can not get lock, but it delete lock file when close write client, now, jobC will get lock, it cause concurrent problem. In our case, jobC will rollback jobA mdt commit which has been succeed commited. So, the data table timeline has the repleaseCommit instance, but mdt without this update, it cause partition path be deleted and can not reserve the latest file split in our case ### Change Logs - will check lock create_time in memory before delete lock file - only lock owner or lock is expired can delete lock ### Impact - the lock file may always exist. If the process exits normally and the expiration time is not set up ### Risk level (write none, low medium or high below) medium ### Documentation Update None ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Change Logs and Impact were stated clearly - [ ] Adequate tests were added if applicable - [ ] CI passed -- 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: commits-unsubscr...@hudi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
