use latest juju/txn #7284
Merged
use latest juju/txn #7284
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
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.
Description of change
When running mgopurge against older Juju repositories, we found it doesn't do well with very large (2M+) txn collections on mongo 2.4. This brings in the fix for that. Its my understanding that Juju controllers on Trusty still use Mongo 2.4.
QA steps
Running Juju against Mongo 2.4 with very large txn collections should successfully prune the txn collection instead of getting an error about the aggregation document being too large.
Documentation changes
None
Bug reference
juju/txn reference issue: juju/txn#31