2011shenlin opened a new issue, #80: URL: https://github.com/apache/rocketmq-eventbridge/issues/80
This document is mainly used to explain how to handle exceptions when encountering exceptions at runtime.Here are a few concepts that need to be introduced: ## Retry Strategy The strategies for retrying when an exception is encountered. This is an enumeration value: * EXPONENTIAL_DECAY_RETRY Exponentially decaying retries. Retry 176 times, and the interval between each retry increases exponentially to 512 seconds, and the total retry time is 1 day. The specific intervals of each retry are: 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 512, ..., 512 seconds (a total of 167 retries and 512 seconds). * REGULAR_INTERVAL_RETRY Retry at a fixed time interval. The default retry is 3 times. The interval between each retry is a random value between 10 seconds and 20 seconds. ‘EXPONENTIAL_DECAY_RETRY’ is the default value. ## Errors Tolerance Whether to tolerate exceptions when encountering exceptions. This is an enumeration value: * ALL Skip over problematic records. EventBridge will continue to push events downstream. * NONE Pause the current push task. ‘ALL’ is the default value. ## Dead Letter Queue When the number of retries is reached and the event is still not successfully pushed, the event will be sent to the dead letter queue(DLQ). The default dead letter pair supported by the current system is RocketMQ, and you can specify where the dead letter is written by configuring the Topic Name. All the properties can be configed in the 'RunOptionsDTO' when create event targets. -- 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]
