On Wed, Sep 9, 2015 at 12:09 PM, Vasileios Vlachos < vasileiosvlac...@gmail.com> wrote:
> In our case the restart bit has already been done. Do you know if it would > be a bad idea to create a new KS before all nodes have upgraded their > SSTables? > This particular case is probably fine. The reason for the caution against issuing certain kinds of queries during a rolling restart is twofold : 1) TRUNCATE requires all known nodes to be available to succeed, if you are restarting one, it won't be available. 2) in theory, the newly upgraded nodes might not get the DDL schema update properly due to some incompatible change To check for 2, do : " nodetool gossipinfo | grep SCHEMA |sort | uniq -c | sort -n " Before and after and make sure the schema propagates correctly. There should be a new version on all nodes between each DDL change, if there is you will likely be able to see the new schema on all the new nodes. Test in a test environment with the specific versions before trying in production. =Rob
