You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/user-guide/en/cap/configuration.md
+8-1
Original file line number
Diff line number
Diff line change
@@ -152,4 +152,11 @@ By default, CAP will only read one message from the message queue, then execute
152
152
If set to true, the consumer will prefetch some messages to the memory queue, and then distribute them to the .NET thread pool for execution.
153
153
154
154
!!! note "Precautions"
155
-
Setting it to true may cause some problems. When the subscription method executes too slowly and takes too long, it will cause the retry thread to pick up messages that have not yet been executed. The retry thread picks up messages from 4 minutes (FallbackWindowLookbackSeconds) ago by default , that is to say, if the message backlog of more than 4 minutes (FallbackWindowLookbackSeconds) on the consumer side will be picked up again and executed again
155
+
Setting it to true may cause some problems. When the subscription method executes too slowly and takes too long, it will cause the retry thread to pick up messages that have not yet been executed. The retry thread picks up messages from 4 minutes (FallbackWindowLookbackSeconds) ago by default , that is to say, if the message backlog of more than 4 minutes (FallbackWindowLookbackSeconds) on the consumer side will be picked up again and executed again
156
+
157
+
#### EnablePublishParallelSend
158
+
159
+
> Default: false， The (7.2 <= Version < 8.1) the default behavior is true
160
+
161
+
By default, messages sent are first placed into the Channel in memory and then processed linearly.
162
+
If set to true, the task of sending messages will be processed in parallel by the .NET thread pool, which will greatly increase the speed of sending.
Copy file name to clipboardExpand all lines: docs/content/user-guide/en/cap/messaging.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ Retrying plays an important role in the overall CAP architecture design, CAP ret
125
125
126
126
During the message sending process, when the broker crashes or the connection fails or an abnormality occurs, CAP will retry the sending. Retry 3 times for the first time, retry every minute after 4 minutes (FallbackWindowLookbackSeconds), and +1 retry. When the total number of retries reaches 50, CAP will stop retrying.
127
127
128
-
You can adjust the total number of retries by setting [FailedRetryCount](../configuration#failedretrycount) in CapOptions Or use [FailedThresholdCallback](../configuration#failedthresholdcallback) to receive notifications when the maximum retry count is reached.
128
+
You can adjust the total number of retries by setting [FailedRetryCount](configuration.md#failedretrycount) in CapOptions Or use [FailedThresholdCallback](configuration.md#failedthresholdcallback) to receive notifications when the maximum retry count is reached.
129
129
130
130
It will stop when the maximum number of times is reached. You can see the reason for the failure in Dashboard and choose whether to manually retry.
131
131
@@ -141,10 +141,10 @@ Whether sending fails or consumption fails, we will store the exception message
141
141
142
142
There is an `ExpiresAt` field in the database message table indicating the expiration time of the message. When the message is sent successfully, status will be changed to `Successed`, and `ExpiresAt` will be set to **1 day** later.
143
143
144
-
Consuming failure will change the message status to `Failed` and `ExpiresAt` will be set to **15 days** later (You can use [FailedMessageExpiredAfter](../configuration#failedmessageexpiredafter) configuration items to custom).
144
+
Consuming failure will change the message status to `Failed` and `ExpiresAt` will be set to **15 days** later (You can use [FailedMessageExpiredAfter](configuration.md#failedmessageexpiredafter) configuration items to custom).
145
145
146
146
By default, the data of the message in the table is deleted every **5 minutes** to avoid performance degradation caused by too much data. The cleanup strategy `ExpiresAt` is performed when field is not empty and is less than the current time.
147
147
148
148
That is to say, the message with the status Failed (by default they have been retried 50 times), if you do not have manual intervention for 15 days, it will **also be** cleaned up.
149
149
150
-
You can use [CollectorCleaningInterval](../configuration#collectorcleaninginterval) configuration items to custom the interval time.
150
+
You can use [CollectorCleaningInterval](configuration.md#collectorcleaninginterval) configuration items to custom the interval time.
process-id： The ID of the CAP process to collect counter data from.
73
73
74
-
74
+
75
75
76
76
### Monitor with dashboard
77
77
78
78
You can configure `x.UseDashboard()` to open the dashboard to view Metrics graph charts.
79
79
80
-
80
+
81
81
82
82
In the Realtime Metric Graph, the time axis will scroll in real time over time so that you can see the rate of publishing and consuming messages per second, And the consumer execution time is "dotted" on the Y1 axis (Y0 axis is the rates, and the Y1 axis is the execution elpsed time).
Copy file name to clipboardExpand all lines: docs/content/user-guide/en/transport/aws-sqs.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -32,15 +32,15 @@ public void TestBar(DateTime value)
32
32
```
33
33
After CAP startups, you will see in SNS management console:
34
34
35
-
35
+
36
36
37
37
### SQS
38
38
39
39
For each consumer group, CAP will create a corresponding SQS queue, the name of the queue is the name of the `DefaultGroup` in the configuration options, and the queue type is Standard.
40
40
41
41
The SQS queue will subscribe to Topic in SNS, as shown below:
42
42
43
-
43
+
44
44
45
45
!!! warning "Precautions"
46
46
Due to the limitation of AWS SNS, when you remove the subscription method, CAP will not delete topics or queues on AWS SNS or SQS, you need to delete them manually.
| AutoCompleteMessages | Gets a value that indicates whether the processor should automatically complete messages after the message handler has completed processing | bool | false |
50
-
| CustomHeaders | Adds custom and/or mandatory Headers for incoming messages from heterogeneous systems. |`Func<Message, List<KeyValuePair<string, string>>>?`| null |
51
-
| Namespace | Namespace of Servicebus , Needs to be set when using with TokenCredential Property | string | null |
52
-
| SQLFilters | Custom SQL Filters by name and expression on Topic Subscribtion | List<KeyValuePair<string, string>> | null |
| AutoCompleteMessages | Gets a value that indicates whether the processor should automatically complete messages after the message handler has completed processing | bool | false |
50
+
| CustomHeaders | Adds custom and/or mandatory Headers for incoming messages from heterogeneous systems. |`Func<Message, List<KeyValuePair<string, string>>>?`| null |
51
+
| Namespace | Namespace of Servicebus , Needs to be set when using with TokenCredential Property | string | null |
52
+
| DefaultCorrelationHeaders | Adds additional correlation properties to all [correlation filters](https://learn.microsoft.com/en-us/azure/service-bus-messaging/topic-filters#correlation-filters). | IDictionary<string, string> | Dictionary<string, string>.Empty |
53
+
| SQLFilters | Custom SQL Filters by name and expression on Topic Subscribtion | List<KeyValuePair<string, string>> | null |
When the message sent from a heterogeneous system, because of the CAP needs to define additional headers, so an exception will occur at this time. By providing this parameter to set the custom headersn to make the subscriber works.
48
48
49
-
You can find the description of heterogeneous system integration [here](../../cap/messaging#heterogeneous-system-integration).
49
+
You can find the description of heterogeneous system integration [here](../cap/messaging.md#heterogeneous-system-integration).
50
50
51
51
Sometimes, if you want to get additional context information from Broker, you can also add it through this option. For example, add information such as Offset or Partition.
Servers | Server url/urls used to connect to the NATs server. | string | NULL
43
43
ConnectionPoolSize | number of connections pool | uint | 10
44
-
DeliverPolicy | The point in the stream to receive messages from | enum | DeliverPolicy.New
44
+
DeliverPolicy | The point in the stream to receive messages from (⚠️ Removed from version 8.1.0, use `ConsumerOptions` instead.) | enum | DeliverPolicy.New
Copy file name to clipboardExpand all lines: docs/content/user-guide/en/transport/rabbitmq.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ services.AddCap(x =>
74
74
75
75
When the message sent from the RabbitMQ management console or a heterogeneous system, because of the CAP needs to define additional headers, so an exception will occur at this time. By providing this parameter to set the custom headersn to make the subscriber works.
76
76
77
-
You can find the description of [Header Information](../cap/messaging#heterogeneous-system-integration) here.
77
+
You can find the description of [Header Information](../cap/messaging.md#heterogeneous-system-integration) here.
0 commit comments