On 31.05.2017 09:34, Stefania Alborghetti wrote: > There shouldn't be too many people with 3.0.13 in > production however, since upgrading to 3.0.13 is broken in the first place.
Keep in mind that there are always people upgrading from 2.x, especially since we had a couple of important bug fixes for 2.x -> 3.0 that people might have been waiting for before taking the plunge. We should at least be so kind to let these users know about potential issues in NEWS.txt. If I understand correctly, this will cause schema migration storms across nodes for .13 -> .14. I'd rather see us pulling 3.0.13 from downloads now and take some more time to figure out what can be done for users already running 3.0.13 on production, instead of rushing .14 and risk throwing .13 users under the bus. E.g. can we create a nodetool command to disable execution of schema migration tasks, which can be run during cluster upgrades in cases like this? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
