[FIXED] Panic on raft write issue #766
Merged
Conversation
This file contains 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
An user reported the panic due to a volume full issue and was asking if we could print a more explicit error message. It seems that there is an issue with Boltdb and a recent param called NoFreelistSync. When set to true and a transaction is rolled-back, a panic occurs. This boolean was used when moving from boltdb to etcd/bbolt in the recent 0.12.0 release. Disabling for now until the underlying issue can be resolved. Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
kozlovic
added a commit
that referenced
this pull request
Dec 11, 2019
This option had been disabled due to a defect in bbolt implementation. Since it has been fixed, re-enable it. Was commented out in #766 Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
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.
An user reported the panic due to a volume full issue and was
asking if we could print a more explicit error message (#754)
It seems that there is an issue with Boltdb and a recent param
called NoFreelistSync. When set to true and a transaction is
rolled-back, a panic occurs.
This boolean was used when moving from boltdb to etcd/bbolt
in the recent 0.12.0 release.
Disabling for now until the underlying issue can be resolved.
Signed-off-by: Ivan Kozlovic ivan@synadia.com