Shekharrajak opened a new issue, #69961: URL: https://github.com/apache/doris/issues/69961
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Version current trunk version https://github.com/apache/doris/commit/5af2df323190986392ef221f82a37053efc30d20 ### What's Wrong? In shared-nothing mode, failed transaction aborts can leave the Routine Load job write lock held, blocking subsequent job operations. This affects existing classic Kafka Routine Load. beforeAborted() acquires the job lock; afterAborted() releases it. Failure during abort processing must still release that lock. Late abort: COMMITTED txn -> acquire job lock -> abort rejected -> cleanup skipped -> lock remains held Journal error: acquire job lock -> transition to ABORTED -> persist/enqueue throws -> cleanup skipped -> lock remains held Both ordinary and 2PC abort paths can skip the cleanup callback when an exception occurs. ### What You Expected? beforeAborted succeeds -> try abort/persist -> finally afterAborted -> release job lock -> return original outcome - Pair every successful before callback with its after callback. - Execute cleanup outside the transaction monitor. - Preserve the abort failure; a rejected abort leaves the transaction COMMITTED. - Retain delete-job callbacks when no abort occurred, so the cleanup change preserves pending delete completion. ### How to Reproduce? _No response_ ### Anything Else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
