curved-magazine-23582
07/14/2021, 3:49 AMStarting upgrade with id NoCodeDataMigration...
Cleanup has not been requested.
Skipping Step 1/7: RemoveAspectV2TableStep...
Executing Step 2/7: GMSQualificationStep...
Completed Step 2/7: GMSQualificationStep successfully.
Executing Step 3/7: UpgradeQualificationStep...
-- V1 table exists
-- V1 table has 8011 rows
-- V2 table exists
-- V2 table has 2 rows
-- Since V2 table has records, we will not proceed with the upgrade.
-- If V2 table has significantly less rows, consider running the forced upgrade.
Failed to qualify upgrade candidate. Aborting the upgrade...
Step with id UpgradeQualificationStep requested an abort of the in-progress update. Aborting the upgrade...
Upgrade NoCodeDataMigration completed with result ABORTED. Exiting...
How do I do that recommended forced upgrade
in this case?mammoth-bear-12532
--force-upgrade
to your command line invocation.curved-magazine-23582
07/14/2021, 4:07 AM./run_upgrade.sh --force-upgrade
?mammoth-bear-12532
mammoth-bear-12532
mammoth-bear-12532
mammoth-bear-12532
curved-magazine-23582
07/14/2021, 4:10 AMcurved-magazine-23582
07/14/2021, 4:10 AMmammoth-bear-12532
./datahub-upgrade.sh -u NoCodeDataMigration
?curved-magazine-23582
07/14/2021, 4:14 AMmammoth-bear-12532
mammoth-bear-12532
mammoth-bear-12532
run_upgrade.sh
is invoking a specific set of args for datahub-upgrade.
cd $DIR && ../datahub-upgrade.sh -u NoCodeDataMigration -a batchSize=1000 -a batchDelayMs=100
mammoth-bear-12532
-a force-upgrade
to that list of argsmammoth-bear-12532
mammoth-bear-12532
mammoth-bear-12532
./datahub-upgrade.sh -u NoCodeDataMigration -a batchSize=500 -a batchDelayMs=1000 -a force-upgrade
mammoth-bear-12532
docker
directorymammoth-bear-12532
mammoth-bear-12532
curved-magazine-23582
07/14/2021, 4:29 AMcurved-magazine-23582
07/14/2021, 4:47 AMbig-carpet-38439
07/14/2021, 1:05 PM