Set dashboard timeout thresholds to reduce disconnects #178
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Explicitly set various dashboard timeout thresholds.
Changes
Note: I am unable to get the
app_session_timeoutkey (and other keys restricted to Shiny Server Pro) to be recognized locally. However, assuming we have Shiny Server Pro, this should work in staging and prod.Fixes
Decrease the rate of app disconnects.
Letting a given app session last longer improves the caching behavior from #169. Since the data cache is stored in memory, if the session closes we need to reload and re-cache the data.