POC: Check available space before writing #1400
Draft
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
Try to check available space before writing to ensure that we could rollback from 'no space left' situation as leveldb requires space even for delete operations. Relates-To: OAM-2013 Signed-off-by: Andrey Kashcheev <ext-andrey.kashcheev@here.com>
Codecov Report
@@ Coverage Diff @@
## master #1400 +/- ##
==========================================
- Coverage 80.71% 80.70% -0.01%
==========================================
Files 337 337
Lines 12600 12624 +24
Branches 1360 1363 +3
==========================================
+ Hits 10170 10188 +18
- Misses 1881 1887 +6
Partials 549 549
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Try to check available space before writing to ensure that we could rollback from 'no space left' situation as leveldb requires space even for delete operations.
Relates-To: OAM-2013