QoS策略_qos 策略、qos 规则的生命周期管理-CSDN博客

本文链接：https://blog.csdn.net/qq_37174816/article/details/126524000

本文详细介绍了在消息传递系统中不同QoS（服务质量）策略之间的兼容性，包括可靠性、持久性、截止时间等关键策略的设置及其相互作用。通过表格形式清晰地展示了各种策略组合是否能够成功建立连接。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

History
- Keep last: only store up to N samples, configurable via the queue depth option.
- Keep all: store all samples, subject to the configured resource limits of the underlying middleware.
Depth
- Queue size: only honored if the “history” policy was set to “keep last”.
Reliability
- Best effort: attempt to deliver samples, but may lose them if the network is not robust.
- Reliable: guarantee that samples are delivered, may retry multiple times.
Durability
- Transient local: the publisher becomes responsible for persisting samples for “late-joining” subscriptions.
- Volatile: no attempt is made to persist samples.
Deadline
- Duration: the expected maximum amount of time between subsequent messages being published to a topic
Lifespan
- Duration: the maximum amount of time between the publishing and the reception of a message without the message being considered stale or expired (expired messages are silently dropped and are effectively never received).
Liveliness
- Automatic: the system will consider all of the node’s publishers to be alive for another “lease duration” when any one of its publishers has published a message.
- Manual by topic: the system will consider the publisher to be alive for another “lease duration” if it manually asserts that it is still alive (via a call to the publisher API).
Lease Duration
- Duration: the maximum period of time a publisher has to indicate that it is alive before the system considers it to have lost liveliness (losing liveliness could be an indication of a failure).