forked from apple/foundationdb
-
Notifications
You must be signed in to change notification settings - Fork 6
Merged upstream 7.1.31 #68
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
Conversation
This file contains hidden or 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
When VV is enabled, the comparison of storage server version and read version should use the original read version, otherwise, the client may get the wrong transaction_too_old error.
Fix transaction_too_old error when version vector is enabled
Cherry pick PR 8630 to release 7.1
This is a patch to release-7.1 after resolving conflicts from commit in main branch, in order to enable byteLimit in release-7.1 A fraction of byteLimit will be used as the limit to fetch index. For the indexes fetched, fetch records for them in batch. byteLimit always count the index size, it also count record if exist, it at least return 1 index-record entry and always include the last entry despite that adding the last entry despite it might exceed limit. There is a Knob STRICTLY_ENFORCE_BYTE_LIMIT, when it is set, records will be discarded once the byteLimit is hit, despite they are fetched. Otherwise, return the whole batch.
This reverts commit fadcb08.
* Add SS read range bytes metrics. (apple#8697) * Fix build failure * clang-fmt * fmt
add bytelimit for prefetch (release-7.1)
Rocksdb suggest compact range checks
RocksDB 7.7.3 version upgrade
The number of released bytes exceeds the number of acquired bytes in locks. This is because the bytes counted towards release is calculated after a "wait", when more bytes could be allocated.
Fix backup worker assertion failure [release-7.1]
To fix simulation failures where the knob value is too small.
Fix specialkeyspace workload [release-7.1]
Update info trigger new DB info update immediately [release-7.1]
* Don't block the exclusion of stateless processes by the free capacity check * Fix syntax * Make use of precomputed exclude check * Format code * Only consider newly excluded processes * Format code and update comment
…test [release-7.1] (apple#9785) * Fix finishedQueries metric, add metrics reporting in GetMappedRange test * refactor to make format work * resolve comments * Fix more comments * Fix bugs and change running time of test
…Servers if the input list is already excluded/failed (apple#9809) * Add a check in excludeServer function that if the exclusion list already exists, don't need to issue new writes. * Update documentation
Also retry when operation_cancelled happens
…stead of bytelimit.
FdbServer not able to join cluster Co-authored-by: Jingyu Zhou <[email protected]>
Update 7.1.30 release notes [release-7.1]
…le#9904) * Fixed stuck data movement when a server is removed When a server is removed, dataDistributionRelocator doesn't remove the work for the destination storage workers. As a result, it can no long move shard into any of the healthy workers in the destination team. * Avoid double complete the work
# Conflicts: # CMakeLists.txt # cmake/CompileRocksDB.cmake # documentation/sphinx/requirements.txt # documentation/sphinx/source/release-notes/release-notes-710.rst # fdbclient/ServerKnobs.cpp # fdbclient/ServerKnobs.h # fdbserver/KeyValueStoreRocksDB.actor.cpp # fdbserver/RocksDBCheckpointUtils.actor.h # fdbserver/storageserver.actor.cpp # fdbserver/workloads/GetMappedRange.actor.cpp
foxyholic
approved these changes
Apr 10, 2023
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.
No description provided.