Reattaching the two logs with only the 1.1 patch applied. Putting asides all the truncation related EOFException for now:
- on node1 (the 1.1 node), we do see a "Can't accept schema migrations from Cassandra versions previous to 1.1, please update first", though I suppose it would be nice to avoid the 'Fatal exception' and stacktrace that tends to scare people.
- on node2, we still have "UnsupportedOperationException: Not a time-based UUID" exceptions.
That being said, even if we fix all those exceptions (which we should, there no question on that), it is still the case that the schema change is applied to the 1.0 nodes and no error is returned to the user (that is, outside of the log file), but the added column family is not really usable (the user will get timeouts) at least until the cluster upgrade is complete. Even if the user do watch the log and see the error (and will probably assume the creation failed), the column family is still created. That's not really user friendly. So I still think it would be a good idea to add code to 1.0 and 1.1 to refuse upfront schema changes when the cluster is known to have mixed pre-1.1/post-1.1 versions. That don't necessarily mean we would require an upgrade to 1.0.8+ before upgrading to 1.1, but it would mean that for all those that does upgrade from 1.0.8 (possibly a majority of users), we're being more user friendly.