Thanks Paul. This is interesting.
So, anything I need to do after cp? - nodetool repair?
Also I am assuming I need to be doing this exercise on all the nodes of the
cluster - right?
Any suggestion to automate this or do it just from a single node?
— Ankit Gadhiya
On Tue, Oct 29, 2019 at 11:21
Straight up Unix cp command, make sure you're in the right directory. If
you try to use schema.cql then you're going to have to massage it somewhat
due to keyspace name differences and schema changes over time. You'll see
what I mean if you've got some.
It goes without saying that you're gonna
If you’re planning to restore snapshot to target keyspace in same cluster – you
can:
1. Take snapshot and copy snapshots to shared volume like NFS share so
later you can load sstables using sstables loader from single node.
2. Make sure you create target keyspace and tables (without
Thanks Alex. We have 6 nodes in each DC with RF=3 with CL local qourum .
and we stopped and started only one instance at a time . Tough nodetool
status says all nodes UN and system.log says canssandra started and started
listening . Jmx explrter shows instance stayed down longer how do we
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0-alpha2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.5.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.19.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.15.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of
On Tue, Oct 29, 2019 at 9:34 PM Rahul Reddy
wrote:
>
> We have our infrastructure on aws and we use ebs storage . And aws was
> retiring on of the node. Since our storage was persistent we did nodetool
> drain and stopped and start the instance . This caused 500 errors in the
> service. We have
Hello,
We have our infrastructure on aws and we use ebs storage . And aws was
retiring on of the node. Since our storage was persistent we did nodetool
drain and stopped and start the instance . This caused 500 errors in the
service. We have local_quorum and rf=3 why does stopping one instance
Hi folks,
I'm looking at a table that has a primary key defined as "publisher_id
text". I've noticed some of the entries have what appears to me to be
a UTF-8 BOM marker and some do not.
https://docs.datastax.com/en/archived/cql/3.3/cql/cql_reference/cql_data_types_c.html
says text is a UTF-8
Thanks folks for your responses but still haven't found concrete solution
for this.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 2:15 PM Sergio Bilello
wrote:
> Rolling bounce = Rolling repair per node? Would not it be easy to be
> scheduled with Cassandra Reaper?
> On
Rolling bounce = Rolling repair per node? Would not it be easy to be scheduled
with Cassandra Reaper?
On 2019/10/29 15:35:42, Paul Carlucci wrote:
> Copy the schema from your source keyspace to your new target keyspace,
> nodetool snapshot on your source keyspace, copy the SSTable files over,
Thanks Paul.
Copy SSTable - How? Using SSTableLoader or some other mechanism.
*Thanks & Regards,*
*Ankit Gadhiya*
On Tue, Oct 29, 2019 at 11:36 AM Paul Carlucci
wrote:
> Copy the schema from your source keyspace to your new target keyspace,
> nodetool snapshot on your source keyspace, copy
Copy the schema from your source keyspace to your new target keyspace,
nodetool snapshot on your source keyspace, copy the SSTable files over, do
a rolling bounce, repair, enjoy. In my experience a rolling bounce is
easier than a nodetool refresh.
It's either that or just copy it with Spark.
On
Thanks Alex. So How do I copy SSTables from 1.0 to 2.0? (Same SSTableLoader
or any other approach?)
Also since I've multi-node cluster - I'll have to do this on every single
node - is there any tool or better way to execute this just from a single
node?
*Thanks & Regards,*
*Ankit Gadhiya*
On
You can create all tables in new keyspace, copy SSTables from 1.0 to 2.0
tables & use nodetool refresh on tables in KS 2.0 to say Cassandra about
them.
On Tue, Oct 29, 2019 at 4:10 PM Ankit Gadhiya
wrote:
> Hello Folks,
>
> Greetings!.
>
> I've a requirement in my project to setup Blue-Green
Hello Folks,
Greetings!.
I've a requirement in my project to setup Blue-Green deployment for
Cassandra. E.x. Say My current active schema (application pointing to) is
Keyspace V1.0 and for my next release I want to setup Keysapce 2.0 (with
some structural changes) and all testing/validation
18 matches
Mail list logo
