[MM-43508] Implement basic reconnection support for rtcd client #59
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.
Summary
PR adds reconnection support for the rtcd client as implemented in mattermost/rtcd#24
rtcd
instance restarted and wiped its store.maxReconnectAttempts
(default to 8) with some incremental backoff (2 seconds).maxReconnectAttempts
is reached we give up and disable the plugin.To note, this doesn't cover initial connection on plugin startup. Adding that support makes the logic even more complex so I opted to keep the assumption that a running
rtcd
should be available when enabling the plugin.Also, this whole logic is going to change a bit when implementing MM-43872 as we are going to deal with multiple concurrent clients but didn't want to couple the two pieces of work so take this as a first iteration.
Ticket Link
https://mattermost.atlassian.net/browse/MM-43508