You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by du...@apache.org on 2022/01/13 05:48:08 UTC
[rocketmq] branch develop updated: [ISSUE #3751] docs: Fix typos and other little error in the document 'Configuration_Client.md' (#3752)
This is an automated email from the ASF dual-hosted git repository.
duhengforever pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new 8d28d3f [ISSUE #3751] docs: Fix typos and other little error in the document 'Configuration_Client.md' (#3752)
8d28d3f is described below
commit 8d28d3fa20b85ba21362bd3f6ad4b118733710c2
Author: 彭小漪 <64...@qq.com>
AuthorDate: Thu Jan 13 13:48:04 2022 +0800
[ISSUE #3751] docs: Fix typos and other little error in the document 'Configuration_Client.md' (#3752)
---
docs/en/Configuration_Client.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/en/Configuration_Client.md b/docs/en/Configuration_Client.md
index 41b573b..0fcd95f 100644
--- a/docs/en/Configuration_Client.md
+++ b/docs/en/Configuration_Client.md
@@ -42,7 +42,7 @@ HTTP static server addressing is recommended, because it is simple client deploy
#### 2.1 Client Common Configuration
-| Pamater Name | Default Value | Description |
+| Parameter Name | Default Value | Description |
| ----------------------------- | ------- | ------------------------------------------------------------ |
| namesrvAddr | | Name Server address list, multiple NameServer addresses are separated by semicolons |
| clientIP | local IP | Client local ip address, some machines will fail to recognize the client IP address, which needs to be enforced in the code |
@@ -54,7 +54,7 @@ HTTP static server addressing is recommended, because it is simple client deploy
#### 2.2 Producer Configuration
-| Pamater Name | Default Value | Description |
+| Parameter Name | Default Value | Description |
| -------------------------------- | ---------------- | ------------------------------------------------------------ |
| producerGroup | DEFAULT_PRODUCER | The name of the Producer group. If multiple producers belong to one application and send the same message, they should be grouped into the same group |
| createTopicKey | TBW102 | When a message is sent, topics that do not exist on the server are automatically created and a Key is specified that can be used to configure the default route to the topic where the message is sent.|
@@ -72,7 +72,7 @@ HTTP static server addressing is recommended, because it is simple client deploy
#### 2.3 PushConsumer Configuration
-| Pamater Name | Default Value | Description |
+| Parameter Name | Default Value | Description |
| ---------------------------- | ----------------------------- | ------------------------------------------------------------ |
| consumerGroup | DEFAULT_CONSUMER | Consumer group name. If multi Consumer belong to an application, subscribe the same message and consume logic as the same, they should be gathered together |
| messageModel | CLUSTERING | Message support two mode: cluster consumption and broadcast consumption |
@@ -93,13 +93,13 @@ HTTP static server addressing is recommended, because it is simple client deploy
#### 2.4 PullConsumer Configuration
-| Pamater Name | Default Value | Description |
+| Parameter Name | Default Value | Description |
| -------------------------------- | ----------------------------- | ------------------------------------------------------------ |
| consumerGroup | DEFAULT_CONSUMER | Consumer group name. If multi Consumer belong to an application, subscribe the same message and consume logic as the same, they should be gathered together |
| brokerSuspendMaxTimeMillis | 20000 | Long polling, Consumer pull message request suspended for the longest time in the Broker in milliseconds |
| consumerTimeoutMillisWhenSuspend | 30000 | Long polling, Consumer pull message request suspend in the Broker over this time value, client think timeout. Unit is milliseconds |
| consumerPullTimeoutMillis | 10000 | Not long polling, timeout time of pull message in milliseconds |
-| messageModel | BROADCASTING | Message support two mode: cluster consumption and broadcast consumption |
+| messageModel | CLUSTERING | Message support two mode: cluster consumption and broadcast consumption |
| messageQueueListener | | Listening changing of queue |
| offsetStore | | Consumption schedule store |
| registerTopics | | Collection of registered topics |