Denovo1998 opened a new pull request, #25579:
URL: https://github.com/apache/pulsar/pull/25579
<!--
### Contribution Checklist
- PR title format should be *[type][component] summary*. For details, see
*[Guideline - Pulsar PR Naming
Convention](https://pulsar.apache.org/contribute/develop-semantic-title/)*.
- Fill out the template below to describe the changes contributed by the
pull request. That will give reviewers the context they need to do the review.
- Each pull request should address only one issue, not mix up code from
multiple issues.
- Each commit in the pull request has a meaningful commit message
- Once all items of the checklist are addressed, remove the above text and
this checklist, leaving only the filled out template below.
-->
<!-- Either this PR fixes an issue, -->
Fixes #xyz
<!-- or this PR is one task of an issue -->
Main Issue: #25514
<!-- If the PR belongs to a PIP, please add the PIP link here -->
PIP: #xyz
<!-- Details of when a PIP is required and how the PIP process work, please
see: https://github.com/apache/pulsar/blob/master/pip/README.md -->
### Motivation
PR #25514 added orphan schema ledger cleanup when concurrent schema creation
loses the schema locator CAS race. However, the cleanup used callback-style
`asyncDeleteLedger` inside `whenComplete`, so the schema storage retry could
continue before the BookKeeper delete callback completed.
This makes the no-orphan-ledger assertion timing-sensitive and weakens the
cleanup guarantee exposed by schema creation. This PR waits for the orphan
ledger delete callback before preserving the original CAS exception and letting
the existing retry flow continue.
### Modifications
- Added a `deleteLedgerAsync` helper in `BookkeeperSchemaStorage` to wrap
`bookKeeper.asyncDeleteLedger` with a `CompletableFuture`.
- Updated the initial schema creation CAS-failure path to wait for orphan
ledger deletion before rethrowing the original `AlreadyExistsException` or
`BadVersionException`.
- Updated the schema locator update CAS-failure path with the same cleanup
behavior, keeping initial creation and update paths consistent.
- Kept deletion failure behavior compatible: delete failures are logged but
do not fail schema creation.
- Refactored schema concurrency test helpers and added coverage for
concurrent compatible schema updates to verify failed CAS attempts do not leave
extra schema ledgers.
### Verifying this change
- [x] Make sure that the change passes the CI checks.
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
*(or)*
This change is already covered by existing tests, such as *(please describe
tests)*.
*(or)*
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end deployment with large payloads
(10MB)*
- *Extended integration test for recovery after broker failure*
### Does this pull request potentially affect one of the following parts:
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
*If the box was checked, please highlight the changes*
- [ ] Dependencies (add or upgrade a dependency)
- [ ] The public API
- [ ] The schema
- [ ] The default values of configurations
- [ ] The threading model
- [ ] The binary protocol
- [ ] The REST endpoints
- [ ] The admin CLI options
- [ ] The metrics
- [ ] Anything that affects deployment
--
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]
