[DD Testability] Add unittest for resuming infligh relocations#7621
Merged
sfc-gh-xwang merged 8 commits intoJul 24, 2022
Conversation
…ture/dd-refactor-incremental
Collaborator
Doxense CI Report for Windows 10
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
Collaborator
Doxense CI Report for Windows 10
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
Collaborator
Doxense CI Report for Windows 10
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
sfc-gh-bvr
reviewed
Jul 21, 2022
| ACTOR static Future<Void> resumeRelocations(Reference<DataDistributor> self) { | ||
| ASSERT(self->shardsAffectedByTeamFailure); // has to be allocated | ||
|
|
||
| ACTOR static Future<Void> resumeFromInitShards(Reference<DataDistributor> self, bool traceShard) { |
Collaborator
There was a problem hiding this comment.
Can the name be simpler, like setupShards?
| return Void(); | ||
| } | ||
|
|
||
| ACTOR static Future<Void> resumeFromInitDataMoveMap(Reference<DataDistributor> self) { |
Collaborator
There was a problem hiding this comment.
Same here - can the name simply be initDataMoveMap?
Collaborator
Author
There was a problem hiding this comment.
I want to retain the resumeFrom which describes the intention more accurately in my opinion.
Collaborator
Doxense CI Report for Windows 10
|
Collaborator
Doxense CI Report for Windows 10
|
Contributor
Result of foundationdb-pr-macos on macOS BigSur 11.5.2
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
Contributor
Result of foundationdb-pr-cluster-tests on Linux CentOS 7
|
sfc-gh-bvr
approved these changes
Jul 23, 2022
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
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.
Add test case "/DataDistributor/Initialization/ResumeFromShard".
There will be an OOM if the number of shards reaches 1 million. So we should limit the shard number also in practice.
Code-Reviewer Section
The general guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branchormainif this is the youngest branch)