Two people say I’m wrong, I’ll believe it - must be imagining restrictions that
don’t exist.
--
Jeff Jirsa
> On Oct 12, 2017, at 10:55 PM, Per Otterström
> wrote:
>
> Hi!
>
> This was news to me. I had the impression that we are maintaining backwards
> compatibility for streaming non-upgr
Hi Jeff,
I was under the impression that streaming in a cluster with mixed binary
versions might be problematic, but as long as the cluster is on the same binary
version (e.g. after a rolling upgrade), we still can have SStables in mixed
data formats and streaming will work?
Thanks,
Thomas
--
Hi!
This was news to me. I had the impression that we are maintaining backwards
compatibility for streaming non-upgraded sstables. Is that not the case?
However, I believe it is a good idea to run upgradesstables at some point
_before_ upgrading Cassandra next time to make sure there are no old
You won't notice any issues (all versions of cassandra are backwards
compatible at least 1 version), and sstables will be slowly migrated to the
new format as you compact, but you should still run it (upgradesstables)
explicitly because when it comes time to run
repair/boostrap/decommission/etc, yo
Hi,
I recently upgraded my test cluster from C* 2.0.9 to 2.1.19 and I did not
run 'nodetool upgradesstables' at all. Per my confirmation afterwards,
everything is fine. But according to documentation at
https://support.datastax.com/hc/en-us/articles/208040036-Nodetool-upgradesstables-FAQ.
I need t
