Hi Rhys,
you can't disable migrations as they are necessary to bring the database up to date so that Reaper can safely start up.
We've added a consensus system in the migration path in master, so that only one Reaper instance can perform the migration. I have no release date for the code in master (but beta builds are available).
We also pushed a PR upstream in the migration library we're using so that it handles the consensus out of the box and Reaper can rely on it directly.
For now, I advise you to start only one Reaper instance when you upgrade, and once it's up start the remaining ones.
Cheers,
-----------------
Alexander Dejanovski
France
@alexanderdeja
Consultant
Apache Cassandra Consulting