removed failed connections from the pool#784
Open
seanmcevoy wants to merge 21 commits intobasho:developfrom
Open
removed failed connections from the pool#784seanmcevoy wants to merge 21 commits intobasho:developfrom
seanmcevoy wants to merge 21 commits intobasho:developfrom
Conversation
Since riak_kv_vnode could have deleted a expired object.
…ords-riak-kv-vnode Replace useage of macro with factory function
Add thumbs.
Use GPB protobuf library.
Thumbs Git Robot Merge.
These warnings no longer exist. Might as well remove them from this file.
…rnings Remove old lines from dialyzer.ignore-warnings
Delete unused compose and multicompose functions
Contributor
|
Does the |
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
9 participants
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.
Attempted fix for issue:
#723
the pid of the dead process was being left in the 'pending' list.
i haven't figured out the original scenario that put it into this state but this bug would have been responsible for the repetitive retries and 'noproc' crashes.