sollhui opened a new pull request, #68342:
URL: https://github.com/apache/doris/pull/68342
### What problem does this PR solve?
Cloud MOW INSERT stopped retrying delete bitmap lock errors and calculation
timeouts after the insert executor switched to the attachment-aware commit
overload. That overload performs one attempt because BE-driven loads already
retry at their caller. Ordinary INSERT is affected even when its attachment is
null.
Add an explicit FE-owned retry entry and reuse the existing cloud retry
loop. Nereids INSERT now uses this entry, preserving the transaction attachment
and table stream updates on every attempt. Keep BE-driven commit entry points
single-attempt, the existing attempt limit and signature lifecycle, and
shared-nothing publish-timeout behavior.
### Release note
Fix cloud MOW INSERT failing on the first retryable delete bitmap
calculation error instead of honoring the configured retry attempts.
### Check List (For Author)
- Test:
- Added focused unit tests for retry success/exhaustion, non-retryable
errors, attachment and stream update preservation, signature cleanup, legacy
callers, BE retry ownership, and shared-nothing publish timeout.
- Updated INSERT executor tests and added an ordinary INSERT dispatch
test.
- Java Checkstyle passed; targeted FE unit-test execution is in progress
after provisioning the Thrift 0.24 compiler required by current master.
- Existing Docker regression coverage:
`test_cloud_mow_retry_txn_interleave` and
`test_cloud_concurrent_calc_dbm_task`. Not run locally: Docker daemon is
unavailable.
- Behavior changed: Yes. FE-driven cloud INSERT retries delete bitmap lock
errors using the existing policy.
- Does this need documentation: No.
--
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]
