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
When Sync Gateway loses the TAP feed, it gets moved to Offline mode. In most cases the desired behaviour is for Sync Gateway to go back online once it's able to connect to the TAP feed again. Currently this requires a manual step - calling the _online endpoint on the Admin API.
I propose that when Sync Gateway goes offline unexpectedly as result of a lost TAP feed (i.e. not via a call to the _offline API endpoint), Sync Gateway should periodically attempt to reconnect to the feed and take itself online without user intervention.
To retain user configuration of this behaviour, we could add an optional disable_reconnect flag to the config that would disable the reconnect behaviour.
The text was updated successfully, but these errors were encountered:
When Sync Gateway loses the TAP feed, it gets moved to Offline mode. In most cases the desired behaviour is for Sync Gateway to go back online once it's able to connect to the TAP feed again. Currently this requires a manual step - calling the _online endpoint on the Admin API.
I propose that when Sync Gateway goes offline unexpectedly as result of a lost TAP feed (i.e. not via a call to the _offline API endpoint), Sync Gateway should periodically attempt to reconnect to the feed and take itself online without user intervention.
To retain user configuration of this behaviour, we could add an optional
disable_reconnect
flag to the config that would disable the reconnect behaviour.The text was updated successfully, but these errors were encountered: