Thank you Vladimir.
> On May 18, 2017, at 12:20 PM, Vladimir Yudovin wrote:
>
> Hi,
> actually each Linux with appropriate Java version (Java 8 for Cassandra 3)
> should be suitable (unless you would like to install with deb/rpm and not
> just tarball)
>
>
> Best
Hi,
actually each Linux with appropriate Java version (Java 8 for Cassandra 3)
should be suitable (unless you would like to install with deb/rpm and not just
tarball)
Best regards, Vladimir Yudovin,
Winguzone - Cloud Cassandra Hosting
On Mon, 15 May 2017 14:34:56 -0400 Nitan
That does sound troubling. You mentioned you're reading at local quorum. Did
you write these control records at quorum, or from the same dc at local quorum?
What CL/DC are the other records written at?
On May 17, 2017 at 10:16:42 AM, Dominic Chevalier (dccheval...@gmail.com) wrote:
Hi Folks,
No you can't do it in one step. Streaming between versions isn't supported
On Thu, May 18, 2017 at 8:26 AM daemeon reiydelle
wrote:
> Yes, or decomission the old one and build anew after new one is operational
>
> “All men dream, but not equally. Those who dream by night in
Yes, or decomission the old one and build anew after new one is operational
“All men dream, but not equally. Those who dream by night in the dusty
recesses of their minds wake up in the day to find it was vanity, but the
dreamers of the day are dangerous men, for they may act their dreams with
I have a need to create another datacenter and upgrade my existing Cassandra
from 2.1.13 to Cassandra 3.0.9.
Can I do this as one step? Create a new Cassandra ring that is version 3.0.9
and replicate the data from an existing ring that is Cassandra 2.1.13?
After replicating to the new ring if
Hi again,
and thanks for the input. It's not tombstoned data I think, but over a
really long time very many rows are inserted over and over again - but
with some significant pauses between the inserts. I found some examples
where a specific row (for example pk=xyz, value=123) exists in more