[mongo] use currentOp for MongoDB 3.1+#3015
Merged
Merged
Conversation
This breaks the build until mongodb 3.2.10 tarballs are uploaded to the dd-agent-tarball-mirror S3 bucket
yannmh
changed the title
currentOp for MongoDB 3.1+
yannmh
force-pushed
the
yann/mongodb-fsynclocked-fix
branch
from
November 10, 2016 20:00
c3cabe6 to
aff4c1d
Compare
Author
|
Added the tarball for CI testing. |
Author
|
Tests are 💚 . Merging. |
Contributor
|
Yay |
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
2 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.
Thanks a lot for the fix @lattwood 🙇 .
My 2 cents:
currentOpon MongoDB > = 3.2.0.