Originally from the User Slack
@Roman_Hargrave: maybe we’re missing something obvious or just haven’t tested this by hand, but what is the best way to handle schema changes in a service with multiple instances, e.g. do we need to find some way for the instances to elect a migration runner? in most of our other systems, we are able to start a single pilot/setup/config instance before rolling out the whole deployment, but that’s not an option in this case.
@dor: You just send the CQL statement. Schema changes are transactional and Scylla uses raft and leader election underneath