Close issue #35 #37
Merged
Close issue #35 #37
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
Actually when UpdateStreamAsync is called with high load and WiredTiger, it is possible that the update of stream head throws a MongoDuplicateKeyException. In such a situation we can safely ignore the error, because some other thread already updated the record and we are not able to know which is the latest one.
Now version is handled by the build server, so there is not the need for the single VersionAssemblyInfo.cs anymore.
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.
This is a proposal to close issue #35. Actually there is
another pull request by @mikegore1000 but we think that
a simple try catch (without a retry) is the best solution for the issue.
Actually when UpdateStreamAsync is called with high load
and WiredTiger, it is possible that the update of stream
head throws a MongoDuplicateKeyException. In such a
situation we can safely ignore the error, because some
other thread already updated the record and we are not
able to know which is the latest one.