change mqtt.retry_interval
default value to infinity
#13080
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes EMQX-12281
See also: #12945
Release version: v/e5.8.0
Previous Setting: The default value for
retry_interval
was 30 seconds.New Default: The default
retry_interval
has been changed to 'infinity'. With this update, EMQX will not automatically retry message deliveries by default.Compliance and Compatibility: Aligning with MQTT specification standards, in-session message delivery retries are not typically compliant. We recognize that some users depend on this feature, so the option to configure retries remains available for backward compatibility.
Summary
PR Checklist
Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:
changes/(ce|ee)/(feat|perf|fix|breaking)-<PR-id>.en.md
filesChecklist for CI (.github/workflows) changes
changes/
dir for user-facing artifacts update