Kyrylo Lebediev ,
This worked thanks :-)
wget
http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/cassandra_3.11.2_all.deb
sudo dpkg -i cassandra_3.11.2_all.deb
R1J1
On Sat, Aug 4, 2018 at 12:19 PM, Kyrylo Lebediev <
kyrylo_lebed...@epam.com.invalid> wrote:
> Go to: http://dl.bi
Go to: http://dl.bintray.com/apache/cassandra/pool/main/c/cassandra/
download deb packages for the versions you need and install them by dpkg.
Regards,
Kyrill
From: R1 J1
Sent: Saturday, August 4, 2018 4:56:56 PM
To: user@cassandra.apache.org
Subject: How to downl
You should be able to do:
apt-get install cassandra=3.11.2, the same applies to cassandra-tools
Have a look here: https://askubuntu.com/a/92021
Also, I find useful apt-cache madison to list all the avilable
versions
HTH
On Sat, Aug 4, 2018 at 3:56 PM, R1 J1 wrote:
> What are the steps to dow
This strategy is a lot more work than just replacing nodes one at a time.
For a large cluster it would be months of work instead of a couple days.
On Sat, Aug 4, 2018 at 7:04 AM R1 J1 wrote:
> Can a cluster having 3.11.0 node(s) accept a 3.11.3 node as a new node
> for eventual migration and
Can a cluster having 3.11.0 node(s) accept a 3.11.3 node as a new node
for eventual
migration and decom of older 3.11.0 nodes ?
Can a cluster having 3.11.2(s) node accept a 3.11.3 node as a new node
for eventual migration and decom of older 3.11.2 nodes ?
Regards
R1J1
What are the steps to download the Cassandra 3.11.0 and 3.11.2 binaries
for ubuntu ?
If we follow the steps below they give 3.11.3 binaries but need slightly
older
http://cassandra.apache.org/download/
echo "deb http://www.apache.org/dist/cassandra/debian 311x main" | sudo tee
-a /etc/apt/sourc
Hello!
In case when dynamic snitching is enabled data is read from 'the fastest
replica' and other replicas send digests for CL=QUORUM/LOCAL_QUORUM .
When dynamic snitching is disabled, as the concept of the fastest replica
disappears, which rules are used to choose from which replica to read
I read in some best practising documents on datam model that: do not update old
partitions while using STCS. But i always use cluster keys in my queries and
cqlsh-tracing reports that it only accesses sstables with data having specified
cluster key (not all sstables containing part of partition)
