starting anew. To avoid a cascading failure scenario, a migration is only auto-retried once. If a 2nd tablet failure takes place, it’s up to the user to retry the failed migration. 50 Cross tablet VReplication then the 2nd is a noop, and considered as implicitly successful. Likewise, two DROP TABLE DDLs for same statement will each ensure the table does not exist. If the 1st is successful, then the 2nd has nothing for a period of time, and makes it possible to reinstate the table, populated with all data, via a 2nd revert. • The revert for a DROP relies on the fact that Online DDL DROP TABLE does not, in fact, drop

then the 2nd is a noop, and considered as implicitly successful. Likewise, two DROP TABLE DDLs for same statement will each ensure the table does not exist. If the 1st is successful, then the 2nd has nothing for a period of time, and makes it possible to reinstate the table, populated with all data, via a 2nd revert. • The revert for a DROP relies on the fact that Online DDL DROP TABLE does not, in fact, drop

then the 2nd is a noop, and considered as implicitly successful. Likewise, two DROP TABLE DDLs for same statement will each ensure the table does not exist. If the 1st is successful, then the 2nd has nothing for a period of time, and makes it possible to reinstate the table, populated with all data, via a 2nd revert. • The revert for a DROP relies on the fact that Online DDL DROP TABLE does not, in fact, drop