Dream95 opened a new pull request, #25189:
URL: https://github.com/apache/pulsar/pull/25189
<!--
### 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: #xyz -->
<!-- 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
The binary protocol already performs check backlog quota in `ServerCnx` when
creating producers, but the HTTP REST API path was missing this validation.
~~~Java
.thenAccept(t -> {
// TODO: Check message backlog and fail if backlog too large.
if (!t.isPresent()) {
// Topic not found, and remove from owning partition list.
publishResult.completeExceptionally(new
BrokerServiceException.TopicNotFoundException("Topic not "
+ "owned by current broker."));
TopicName topicName = TopicName.get(topic);
pulsar().getBrokerService().getOwningTopics().get(topicName.getPartitionedTopicName())
.remove(topicName.getPartitionIndex());
~~~
### Modifications
- Added backlog quota checks in `publishSingleMessageToPartition` method for
both `destination_storage` and `message_age` quota types
The implementation follows the same pattern used in
`ServerCnx.handleProducer` where backlog quota checks are performed before
allowing message production.
### Verifying this change
- [x] Make sure that the change passes the CI checks.
This change is already covered by existing tests, such as:
- Existing backlog quota tests should cover this functionality
- HTTP produce endpoint tests should verify the behavior
### 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
- [x] The REST endpoints
- [ ] The admin CLI options
- [ ] The metrics
- [ ] Anything that affects deployment
**Changes to REST endpoints:**
- The HTTP produce endpoint
(`/persistent/{tenant}/{namespace}/{topic}/partitions/{partition}`) now
properly enforces backlog quota limits before publishing messages. When backlog
quota is exceeded, the request will fail with an appropriate error, consistent
with the binary protocol behavior.
### Documentation
<!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
- [ ] `doc` <!-- Your PR contains doc changes. -->
- [ ] `doc-required` <!-- Your PR changes impact docs and you will update
later -->
- [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
- [ ] `doc-complete` <!-- Docs have been already added -->
### Matching PR in forked repository
PR in forked repository: https://github.com/Dream95/pulsar/pull/4
<!--
After opening this PR, the build in apache/pulsar will fail and instructions
will
be provided for opening a PR in the PR author's forked repository.
apache/pulsar pull requests should be first tested in your own fork since
the
apache/pulsar CI based on GitHub Actions has constrained resources and quota.
GitHub Actions provides separate quota for pull requests that are executed
in
a forked repository.
The tests will be run in the forked repository until all PR review comments
have
been handled, the tests pass and the PR is approved by a reviewer.
-->
--
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]
