8000 backport free disk space bugfix from upstream rocksdb by jsteemann · Pull Request #14353 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

backport free disk space bugfix from upstream rocksdb #14353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 28, 2021

Conversation

jsteemann
Copy link
Contributor

Scope & Purpose

Backport of #14352

  • Backport bugfix from upstream rocksdb repository for calculating the free disk space for the database directory (rocksdb PR 8370). Before the bugfix, rocksdb could overestimate the amount of free disk space when the arangod process was run as non-privileged users.
  • 💩 Bugfix (requires CHANGELOG entry)
  • 🍕 New feature (requires CHANGELOG entry, feature documentation and release notes)
  • 🔥 Performance improvement
  • 🔨 Refactoring/simplification
  • 📖 CHANGELOG entry made

Backports:

  • Backports required for: 3.7

Testing & Verification

  • This change is a trivial rework / code cleanup without any test coverage.
  • The behavior in this PR was manually tested

@jsteemann jsteemann added this to the 3.8 milestone Jun 10, 2021
Copy link
Contributor
@fceller fceller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@KVS85 KVS85 added the 3 RocksDB Storage engine related label Jul 28, 2021
@KVS85 KVS85 merged commit 37e9b60 into 3.8 Jul 28, 2021
@KVS85 KVS85 deleted the bug-fix-3.8/backport-rocksdb-diskspace-bugfix branch July 28, 2021 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 RocksDB Storage engine related 9 Ready to Merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0