feat(region,host): add disk migrate support #19991
Merged
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
wanyaoqi
force-pushed
the
feat/disk-storage-migrate
branch
from
ba12d7d to
9d5a7a4
Compare
wanyaoqi
force-pushed
the
feat/disk-storage-migrate
branch
from
9d5a7a4 to
ce4ac0e
Compare
wanyaoqi
force-pushed
the
feat/disk-storage-migrate
branch
2 times, most recently
from
881de59 to
4ce90ed
Compare
wanyaoqi
force-pushed
the
feat/disk-storage-migrate
branch
from
4ce90ed to
4e8674c
Compare
zexi
added a commit
that referenced
this pull request
Apr 16, 2024
…91-upstream-release-3.12 Automated cherry pick of #19991: feat(region,host): add disk migrate support
zexi
added a commit
that referenced
this pull request
Apr 16, 2024
…91-upstream-release-3.11 Automated cherry pick of #19991: feat(region,host): add disk migrate support
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.
What this PR does / why we need it:
Does this PR need to be backport to the previous release branch?:
release/3.11