You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by lh...@apache.org on 2025/09/09 06:48:54 UTC
(pulsar-site) branch main updated: [Doc] Minor fix in concepts-throttling documentation (#1022)
This is an automated email from the ASF dual-hosted git repository.
lhotari pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git
The following commit(s) were added to refs/heads/main by this push:
new 7ab65bfb98a [Doc] Minor fix in concepts-throttling documentation (#1022)
7ab65bfb98a is described below
commit 7ab65bfb98ae9f8085507ce0bc44ab10e082af22
Author: MiguelAMarcelino <mi...@iterable.com>
AuthorDate: Tue Sep 9 07:48:50 2025 +0100
[Doc] Minor fix in concepts-throttling documentation (#1022)
* Minor fix in concepts-throttling documentation
* Improve grammar further
* Update all maintained versions of the docs
---------
Co-authored-by: Lari Hotari <lh...@users.noreply.github.com>
---
docs/concepts-throttling.md | 4 ++--
versioned_docs/version-3.0.x/concepts-throttling.md | 2 +-
versioned_docs/version-4.0.x/concepts-throttling.md | 4 ++--
versioned_docs/version-4.1.x/concepts-throttling.md | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/docs/concepts-throttling.md b/docs/concepts-throttling.md
index 7ba77a0682b..a4ab06d1fd3 100644
--- a/docs/concepts-throttling.md
+++ b/docs/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 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.
- **Limit the allocation of client's hardware resources at topic/subscription levels**
@@ -165,4 +165,4 @@ Message dispatch throttling may cause messages over-delivered per unit of time d
- :::
\ No newline at end of file
+ :::
diff --git a/versioned_docs/version-3.0.x/concepts-throttling.md b/versioned_docs/version-3.0.x/concepts-throttling.md
index c849caf1c8b..044f804ae04 100644
--- a/versioned_docs/version-3.0.x/concepts-throttling.md
+++ b/versioned_docs/version-3.0.x/concepts-throttling.md
@@ -24,7 +24,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 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.
- **Limit the allocation of client's hardware resources at topic/subscription levels**
diff --git a/versioned_docs/version-4.0.x/concepts-throttling.md b/versioned_docs/version-4.0.x/concepts-throttling.md
index 7ba77a0682b..a4ab06d1fd3 100644
--- a/versioned_docs/version-4.0.x/concepts-throttling.md
+++ b/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 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.
- **Limit the allocation of client's hardware resources at topic/subscription levels**
@@ -165,4 +165,4 @@ Message dispatch throttling may cause messages over-delivered per unit of time d
- :::
\ No newline at end of file
+ :::
diff --git a/versioned_docs/version-4.1.x/concepts-throttling.md b/versioned_docs/version-4.1.x/concepts-throttling.md
index 7ba77a0682b..a4ab06d1fd3 100644
--- a/versioned_docs/version-4.1.x/concepts-throttling.md
+++ b/versioned_docs/version-4.1.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 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.
- **Limit the allocation of client's hardware resources at topic/subscription levels**
@@ -165,4 +165,4 @@ Message dispatch throttling may cause messages over-delivered per unit of time d
- :::
\ No newline at end of file
+ :::