Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bridge lazy start type/ relationship between Threshold, idle_timeout and Message Expiry Interval #741

Open
RidhaSoua opened this issue Mar 23, 2018 · 0 comments

Comments

@RidhaSoua
Copy link

Hello,
Mosquitto defines the Lazy start type for the bridge (broker-to-broker communication).
For this Lazy start type, Mosquitto defines the threshold and idle_timeout parameters.
Threshold is the number of messages that need to be queued for a bridge with lazy start type to be restarted. Let’s assume that Threshold is equal to X. Now imagine that we don’t succeed to have the X messages in the queue of the first broker of the bridge (Messages are published in small rate). After an idle_Timeout, the two brokers are disconnected.
Q1: Is there anyway to make this threshold adaptive ? or to make it depends on a timer ?

Q2: Given that messages queued in the first broker have Message Expiry Interval (or TTL), how these parameters (Threshold, Idle_Timeout) work together with the "Message Expiry Interval" of the MQTT messages ?
Because if we wait for a long time before sending messages queued at the first broker of the bridge, these messages do not have any relevance, they become outdated.

Thanks in advance !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant