SHOW VITESS_MIGRATION '...' LOGS, retain logs for 24 hours #8532
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.
Resubmission of #8493, for 11.0 release branch.
Description
Fixes #8178
show vitess_migration '<uuid>' logs
queries, e.g.show vitess_migration '4835ca51_e867_11eb_ab12_0a43f95f28a3' logs
gh-ost
andpt-osc
(but notonline
) migrations generate a migration log, which Vitess stores in a well known location on the primary tablet.It is now possible to view the file, during or after migration. The file is retained for 24 hours after completion/failure.
The command
show vitess_migration '<uuid>' logs
will output the entire log file content for each shard. Therefore, 4 shards => 4 log files.This is tested in
go/test/endtoend/onlineddl/ghost/onlineddl_ghost_test.go
Documentation to follow
Example:
Related Issue(s)
Checklist
Deployment Notes