Low Description
As reported on the mailing list,
- I have a lot of schema updates (there are 2067 rows in the system.Schema CF). - The live node loads migrations 1-1000, and sends them to the recovering node (Migration.getLocalMigrations()) - Soon afterwards, the live node checks the schema version on the recovering node and finds it has moved by a little - say it has applied the first 3 migrations. It then loads migrations 3-1003, and sends them to the node. - This process is repeated very quickly (sends migrations 6-1006, 9-1009, etc).
The source of the problem is that MigrationManager.onChange will send out a full (up to 1000 migrations) replay, every time the target's schema version changes.