storage: correctly apply -inmemoryDataFlushInterval when it's set t…
#6221
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
hagen1778
reviewed
May 7, 2024
Haleygo
force-pushed
the
fix-minimum-inmemoryDataFlushInterval
branch
from
dc4482e
to
f7409b5
Compare
hagen1778
force-pushed
the
fix-minimum-inmemoryDataFlushInterval
branch
from
f7409b5
to
23afd05
Compare
…o minimum supported value 1s
hagen1778
force-pushed
the
fix-minimum-inmemoryDataFlushInterval
branch
from
23afd05
to
78b58f4
Compare
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.
…o minimum supported value 1s
pendingRowsFlushInterval was bumped to 2s in 73f0a80
Checklist
The following checks are mandatory: