You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To mitigate concerns like #74 due to connection storms on the broker, we have had some discussion around introducing a short random delay to the broker reconnection logic.
As an initial number, we discussed up to 30s as a maximum delay.
What is unclear at this time is if this would improve matters during large disconnect/reconnect cycles or have an affect of extend any issues resulting from it.
We discussed internally potential load testing on a non production platform - that would go some way to fine tuning this connection delay.
As a side note, there are other strategies and ongoing works that will further mitigate potential connection storm like issues - however these are not quickly achievable tasks.
Description
To mitigate concerns like #74 due to connection storms on the broker, we have had some discussion around introducing a short random delay to the broker reconnection logic.
As an initial number, we discussed up to 30s as a maximum delay.
What is unclear at this time is if this would improve matters during large disconnect/reconnect cycles or have an affect of extend any issues resulting from it.
We discussed internally potential load testing on a non production platform - that would go some way to fine tuning this connection delay.
As a side note, there are other strategies and ongoing works that will further mitigate potential connection storm like issues - however these are not quickly achievable tasks.
related: #74
related: #98
Epic/Story
No response
Tasks
The text was updated successfully, but these errors were encountered: