Hi team,
I'm currently evaluating TurboMqtt for production use with EMQX. I noticed that the Automatic retry-reconnectfeature currently lacks configuration options for exponential backoff.
Without this, rapid reconnection attempts can easily trigger EMQX's flapping_detectprotection, leading to client bans. Since TurboMqtt is at v0.x, this feels like a sign that the reconnection logic is still maturing.
Could you please consider exposing these parameters (e.g., initial delay, multiplier, max delay) to allow for more robust production deployments?
Thanks!
Hi team,
I'm currently evaluating TurboMqtt for production use with EMQX. I noticed that the Automatic retry-reconnectfeature currently lacks configuration options for exponential backoff.
Without this, rapid reconnection attempts can easily trigger EMQX's flapping_detectprotection, leading to client bans. Since TurboMqtt is at v0.x, this feels like a sign that the reconnection logic is still maturing.
Could you please consider exposing these parameters (e.g., initial delay, multiplier, max delay) to allow for more robust production deployments?
Thanks!