You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "MiguelAMarcelino (via GitHub)" <gi...@apache.org> on 2025/06/24 15:22:45 UTC
[PR] Minor fix in concepts-throttling documentation [pulsar-site]
MiguelAMarcelino opened a new pull request, #1022:
URL: https://github.com/apache/pulsar-site/pull/1022
Fixes a minor syntax error in the pulsar docs.
### ✅ Contribution Checklist
<!--
Feel free to remove the checklist if it does not apply to your PR
-->
- [x] I read the [contribution guide](https://pulsar.apache.org/contribute/document-contribution/)
- [ ] I updated the [versioned docs](https://pulsar.apache.org/contribute/document-contribution/#update-versioned-docs)
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [Doc] Minor fix in concepts-throttling documentation [pulsar-site]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on code in PR #1022:
URL: https://github.com/apache/pulsar-site/pull/1022#discussion_r2332187609
##########
versioned_docs/version-4.0.x/concepts-throttling.md:
##########
@@ -25,7 +25,7 @@ Message dispatch throttling brings the following benefits in detail:
- **Balance the allocation of broker's hardware resources at topic/subscription levels**
- A broker instance serves multiple topics at one time. If a topic is overloaded with requests, it will occupy almost all of the I/O, CPU, and memory resources of the broker, causing other topics cannot be read. Using the message dispatch throttling feature can limit the allocation of broker’s hardware resources across topics.
+ A broker instance serves multiple topics at one time. If a topic is overloaded with requests, it will occupy almost all of the I/O, CPU, and memory resources of the broker, causing other topics to not be read. Using the message dispatch throttling feature can limit the allocation of broker’s hardware resources across topics.
Review Comment:
Thanks for pointing this out. I used Claude to fix grammar here. There were multiple issues.
```suggestion
A broker instance serves multiple topics simultaneously. If a topic becomes overloaded with requests, it will consume nearly all of the broker's I/O, CPU, and memory resources, preventing other topics from being read. Using the message dispatch throttling feature can limit how the broker's hardware resources are allocated across topics.
```
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [Doc] Minor fix in concepts-throttling documentation [pulsar-site]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari commented on PR #1022:
URL: https://github.com/apache/pulsar-site/pull/1022#issuecomment-3269130058
Thanks for the contribution @MiguelAMarcelino
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] [Doc] Minor fix in concepts-throttling documentation [pulsar-site]
Posted by "lhotari (via GitHub)" <gi...@apache.org>.
lhotari merged PR #1022:
URL: https://github.com/apache/pulsar-site/pull/1022
--
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-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org