feat(mongodb-log-writer): skip checks for retentionGB
and maxLogFileCount
when set to Infinity MONGOSH-2047
#515
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.
Because in mongosh (and generally), some of our settings like
logRetentionGB
can be undefined while others likemaxLogFileCount
cannot, it's likely users will end up setting multiple of them asInfinity
if they're looking to unset different things.Our code skips some checks when some steps when those limits are
undefined
but it won't skip if they're infinite so it can be a performance improvement if we skip those steps if their values are infinite as well.