Schedule the migration to start at a given moment.
Parameters:
start: The block number at which the migration will start. DispatchTime calculated
at the moment of the extrinsic execution.
warm_up: Duration or timepoint that will be used to prepare for the migration. Calls
are filtered during this period. It is intended to give enough time for UMP and DMP
queues to empty. DispatchTime calculated at the moment of the transition to the
warm-up stage.
cool_off: The block number at which the post migration cool-off period will end. The
DispatchTime calculated at the moment of the transition to the cool-off stage.
unsafe_ignore_staking_lock_check: ONLY FOR TESTING. Ignore the check whether the
scheduled time point is far enough in the future.
Note: If the staking election for next era is already complete, and the next
validator set is queued in pallet-session, we want to avoid starting the data
migration at this point as it can lead to some missed validator rewards. To address
this, we stop staking election at the start of migration and must wait atleast 1
session (set via warm_up) before starting the data migration.
Read [MigrationStage::Scheduled] documentation for more details.
Schedule the migration to start at a given moment.
Parameters:
start: The block number at which the migration will start.DispatchTimecalculated at the moment of the extrinsic execution.warm_up: Duration or timepoint that will be used to prepare for the migration. Calls are filtered during this period. It is intended to give enough time for UMP and DMP queues to empty.DispatchTimecalculated at the moment of the transition to the warm-up stage.cool_off: The block number at which the post migration cool-off period will end. TheDispatchTimecalculated at the moment of the transition to the cool-off stage.unsafe_ignore_staking_lock_check: ONLY FOR TESTING. Ignore the check whether the scheduled time point is far enough in the future.Note: If the staking election for next era is already complete, and the next validator set is queued in
pallet-session, we want to avoid starting the data migration at this point as it can lead to some missed validator rewards. To address this, we stop staking election at the start of migration and must wait atleast 1 session (set via warm_up) before starting the data migration.Read [
MigrationStage::Scheduled] documentation for more details.