Repository navigation
fallback to in-memory if creating new history session fails - #8846
Merged
Merged
Conversation
Member
Author
|
Related: #2426 |
Member
|
I think is OK as is... |
Carreau
added a commit
that referenced
this pull request
Nov 17, 2015
fallback to in-memory if creating new history session fails
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.
With broken network filesystems, it's probably possible for this to happen at other points, but it seems like the most likely time is creation of the intial session. It could potentially also be in the initialization of the database.