Ariel Weisberg created CASSANDRA-14897:
------------------------------------------
Summary: In mixed 3.x/4 version clusters write tracing and repair
history information without new columns
Key: CASSANDRA-14897
URL: https://issues.apache.org/jira/browse/CASSANDRA-14897
Project: Cassandra
Issue Type: Bug
Components: Distributed Metadata
Reporter: Ariel Weisberg
Assignee: Ariel Weisberg
Fix For: 4.0
In CASSANDRA-14841 I stopped it from writing to those tables so it wouldn't
generate any errors. Aleksey pointed out I could write just the old columns.
If a user manually adds the new columns to the old version nodes before upgrade
they will be able to query this information across the cluster. This is a
better situation then making it completely impossible for people to run repairs
or perform tracing in mixed version clusters.
This would avoid breaking repair and tracing in mixed version clusters.
I also want to properly document how to do this and maybe even provide a script
people can run to add the columns to old nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
