Re: unsubscribe

Sorry to see you go. If you'd like to unsubscribe from the user ML, please email user-unsubscr...@cassandra.apache.org. Cheers! >

Re: java driver with cassandra proxies (option: -Dcassandra.join_ring=false)

Those nodes are not in the peers table(s) because you told them NOT to join the ring with `join_ring=false` so it is working by design. I'm not really sure what you're trying to achieve but if you want to separate the coordinator functions from the storage then what you probably want is to deploy

Re: Questions about high read latency and related metrics

Is it the concept of histograms that's not clear? Something else? >

Re: Questions about high read latency and related metrics

The min/max/mean partition sizes are the sizes in bytes which are the same statistics reported by nodetool tablestats. EstimatedPartitionSizeHistogram is the distribution of partition sizes within specified ranges (percentiles) and is the same histogram reported by nodetool tablehistograms (in

Re: JIRA account creation request for new contributor

Mick has provisioned your account and you should receive a separate email from the jira server with further instructions. Cheers!

Re: JIRA account creation request for new contributor

Welcome! Sorry for the delay. Let me see if I can get your request expedited.  On Tue, 14 Feb 2023 at 07:31, Omair Muhi wrote: > Greetings, > > I would like to request a new JIRA account as I am interested in > contributing to the project. Here is my information: > > >- email address:

Re: Unsubscribe

Sorry to see you go. If you'd like to unsubscribe from the user ML, please email user-unsubscr...@cassandra.apache.org. Cheers!

Re: Change IP address (on 3.11.14)

If (a) the node is part of the cluster, and (b) is running and operational, then (c) the cluster will recognise that the node has a new IP when you restart the node and there's nothing to do on the C* side. A new IP will be handled by C* automatically. Think of situations where a node experiences

Re: Errors while attempting snapshot

Can you help us out by providing more details? When asking questions, it's always a good idea to include background info such as versions and steps to replicate the issue. Cheers!

Re: cassandra.yaml

They are really in mebibytes (MiB). In the upcoming release of Cassandra, the configuration is getting standardised to KiB, MiB, etc, to remove ambiguity (CASSANDRA-15234 [1]). For more info, see Ekaterina Dimitrova's blog post [2]. Cheers! [1]

CASSANDRA DAY - Santa Clara, Bellevue, Houston + FREE private screening of Wakanda Forever! 

[image: cday-20221110-wakanda_forever.png] Calling all developers! The Apache Cassandra community invites you to join an action-packed day of superhero events held simultaneously across 3 cities on November 10 — Santa Clara CA, Bellevue WA and Houston TX! Event info WORKSHOP - Attend in-person

Re: cassandra 4.0.6 files removed from archive

redhat.cassandra.apache.org/40x/ redirects to apache.jfrog.io/artifactory/cassandra-rpm/40x/. When I curl it on the command line, I can see that the cassandra-tools package for 4.0.6 is there. Cheers! cassandra-4.0.6-1.noarch.rpm 25-Aug-2022 09:05 45.43 MB cassandra-4.0.6-1.src.rpm

Re: Upgrade

That's correct. Cheers!

Re: Upgrade

It's just a minor patch upgrade so all you're really upgrading is the binaries. In any case, switching off replication is not the recommended approach. The recommended pre-upgrade procedure is to take backups of the data on your nodes with nodetool snapshot. Cheers!

Re: Cassandra java > 15

Correction -- It has been brought to my attention that there are no plans for 5.0 yet so Java 17 support might be added sooner in the next 4.x release if it's ready. Cheers! > There is no support for Java 17 yet. The plan is to add it in Cassandra > 5.0 [1]. > > [1]

Re: Cassandra java > 15

There is no support for Java 17 yet. The plan is to add it in Cassandra 5.0 [1]. By default, builds are done with Java 8. You can build with Java 11 by setting the flags documented on the site [2]. Cheers! [1] https://issues.apache.org/jira/browse/CASSANDRA-16895 [2]

Re: Local read request going across DC

Just to circle back here, I've reviewed the trace output and it shows multiple requests fired off for lookups on the `roles` table which indicated to me that the default `cassandra` superuser is being used. To be clear, the original read request is being executed at the configured consistency BUT

Re: Local read request going across DC

Would you be open to temporarily posting the full CQL command + full trace output to gist.github.com? I'd like to see what it shows. Cheers! >

Re: Local read request going across DC

It sounds like read-repair chance is enabled on the table. Check the table schema for a non-zero read_repair_chance. Cheers! >

Re: netty connection reset by peer errors in logs

That error message indicates that 2 nodes are unable to communicate with each other over the internode (gossip) port. It makes no sense to suppress it since it's an indication that there's a problem that you need to address. Cheers!

Re: Cassandra 4.0 upgrade - Upgradesstables

As convenient as it is, there are a few caveats and it isn't a silver bullet. The automatic feature will only kick in if there are no other compactions scheduled. Also, it is going to be single-threaded by default so it will take a while to get through all the sstables on dense nodes. In

Re: Cassandra Client compatibility

In the context of driver compatibility, Cassandra "3.0+" means C* 3.0 and newer releases which include C* 3.0.x, 3.11.x, 4.0.x and [soon] 4.1.x. To answer your question directly, version 2.6 of the C++ driver works with C* 3.11.11 but we don't recommend you use it since it's an ancient release

Re: Slow unit tests with Cassandra 4.x on macOS

Johannes, I've copied the Dev ML to hopefully get a wider audience. Cheers! On Wed, 1 Jun 2022 at 21:25, Johannes Weißl wrote: > Hello, > > We noticed that our unit tests are way slower on macOS after the upgrade > from Cassandra 3.11.x to 4.x, e.g. over 8 minutes instead of 30 seconds > (!). >

Re:

Sorry to see you go. If you wish to unsubscribe from the mailing list, please email user-unsubscr...@cassandra.apache.org. Cheers! On Sat, 28 May 2022 at 09:27, Prachi Rath wrote: > unsubscribe > >

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

> > Thank you for that clarification, Erick. So do i understand correctly, > that because of the upgrade the host id changed and therefore differs from > the ones in the sstables where the old host id is still sitting until a > sstable upgrade? > Not quite. :) The host ID will never change for

Re: Upgrade 3.11.6 to 4.0.3, commitlog warns

It's expected and is nothing to worry about. From C* 3.0.25/3.11.11/4.0, the SSTables now contain the host ID on which they were created to prevent loss of commitlog data when SSTables are moved/copied to other nodes (CASSANDRA-16619). That's why the message is logged at WARN level instead of

Re: Malformed IPV6 address

This issue was reported in https://community.datastax.com/questions/13764/ as well. TL;DR the URL parser for JNDI providers was made stricter in Oracle Java 8u331 and brackets are only allowed around IPv6 addresses. The URL format in NodeProbe.java wraps the host in square brackets so nodetool

Re: Cassandra 4.X CqlBulkOutputFormat - mapreduce

> > than you for your response .. But I’m looking for this source in cassandra > 4.x release: > > > https://github.com/AndyHu19900119/cassandra/blob/trunk/examples/hadoop_word_count/src/WordCount.java That was removed a long time ago when Hadoop code was removed in C* 3.0 ( CASSANDRA-9353

Re: Cassandra 4.X CqlBulkOutputFormat - mapreduce

Is this what you are looking for? https://github.com/apache/cassandra/blob/cassandra-4.0.3/src/java/org/apache/cassandra/hadoop/cql3/CqlBulkOutputFormat.java

CALLING ALL CASSANDRA USERS - The Community would love to hear from you!

Are you using Cassandra in production today? Is your organisation building an app with Cassandra as the backend? Is your organisation evaluating or building a POC on Cassandra? If you answered yes to ANY of the questions above, we want to hear from you! The Cassandra Community is always

Re: Cassandra commitlog corruption on hard shutdown

Thanks for circling back and posting your experience! >

Re: upgrade from 3.11 to 4.0

The general advice is to always upgrade to 3.11.latest before upgrading to 4.0.latest. It is possible to upgrade from an older 3.11 version but you'll probably run into known issues already fixed in the latest version. Also, we recommend you run upgradesstables BEFORE upgrading to 4.0.latest --

Re: Cassandra 3.0.14 transport completely blocked

> > Thanks, Scott, for the prompt response! We will apply this patch and see > how it goes. > Also, in the near future, we will consider upgrading to 3.0.26 and > eventually to 4.0 > We would really discourage you from just upgrading to C* 3.0.21. There really is no logical reason for doing that.

Re: Unsolicited emails from IRONMAN Monttremblant

Thanks for bringing it up. I've been meaning to look into this. It got annoying enough for me today that I got ASF Infra team to investigate and the offending address has now been removed from the list ( https://issues.apache.org/jira/browse/INFRA-22879). Cheers!

Re: [RELEASE] Apache Cassandra 4.0.2 released

(moved dev@ to BCC) > It looks like the otc_coalescing_strategy config key is no longer > supported in cassandra.yaml in 4.0.2, despite this not being mentioned > anywhere in CHANGES.txt or NEWS.txt. > James, you're right -- it was removed by CASSANDRA-17132

Re: Cassandra 4.0 upgrade from Cassandra 3x

Make sure you go through all the instructions in https://github.com/apache/cassandra/blob/trunk/NEWS.txt. It's also highly recommended that you upgrade to the latest 3.0.x or 3.11.x version before upgrading to 4.0. Generally there are no changes required on the client side apart from setting the

Re: Running enablefullquerylog crashes cassandra

Are there really no entries after those INFO messages? That indicates that a person/script/daemon/tool/process killed Cassandra. Perhaps check the OS logs to see if oom-killer kicked in to see if the C* process was terminated. Cheers! >

Re: TLS/SSL overhead

The 3-5% penalty range is consistent with what other users have reported over the years but I'm sorry that I can't seem to find the threads/references so my response is unfortunately anecdotal. More importantly, would you be interested in sharing your data? It would be great to feature it as a

Re: Cassandra internal bottleneck

How many clients do you have sending write requests? In several cases I've worked on, the bottleneck is on the client side. Try increasing the number of app instances and you might find that the combined throughput increases significantly. Cheers!

Re: Problem on setup Cassandra v4.0.1 cluster

TP stats indicate pending gossip. Check that the times are synchronised on both nodes (use NTP) since it can prevent gossip from working. I'd also suggest looking at the logs on both nodes to see what other WARN and ERROR messages are being reported. Cheers!

Re: Cassandra 4.0 hanging on restart

I just came across this thread and noted that you're running repairs with -pr which are not incremental repairs. Was that a typo? Cheers!

Re: Migration between Apache 4.x and DSE 6+?

DSE 6.x is compatible with C* 3.11. In any case, there are a lot of sharp edges with mixing OSS C* and DSE nodes so it's not recommended. It is going to be addressed in a future release. Cheers!

Re: Error in bootstrapping node

The error you're seeing is specific to DSE so your best course of action is to log a ticket with DataStax Support (https://support.datastax.com). Cheers!

Re: Which source replica does rebuild stream from?

Yes, you are correct that the source may not necessarily be fully consistent. But this risk is negligible if your cluster is sized-correctly and nodes are not dropping mutations. If your nodes are dropping mutations because they're overloaded and cannot keep up with writes, rebuild is probably

Re: unsubscribe

Hey, mate. You'll need to email user-unsubscr...@cassandra.apache.org to unsubscribe from the list. Cheers!

Re: 4.0.1 - adding a node

Out of curiosity, what's up with hercules and chaos? Do you have different hardware deployed in your cluster? Cheers! >

Re: Schema collision results in multiple data directories per table

> > Erick, one last question: Is there a quick and easy way to extract the > date from a time UUID? > Yeah, just use any online converters on the web. Cheers!

Re: Schema collision results in multiple data directories per table

I agree with Jeff that this isn't related to ALTER TABLE. FWIW, the original table was created in 2017 but a new version got created on August 5: - 20739eb0-d92e-11e6-b42f-e7eb6f21c481 - Friday, January 13, 2017 at 1:18:01 GMT - 8ad72660-f629-11eb-a217-e1a09d8bc60c - Thursday, August 5,

Re: Problem with www.apache.org/dist/cassandra/KEYS?

There was a problem with keys reported yesterday on ASF Slack that Brandon Williams (driftx) fixed early in my morning (I'm based in Australia). Perhaps try again. For reference, the Slack conversation is available here -- https://the-asf.slack.com/archives/CJZLTM05A/p1633538881180500. Cheers! >

Re: Vulnerability in libthrift library (CVE-2019-0205)

See https://issues.apache.org/jira/browse/CASSANDRA-15420. It only applies if you're still using Thrift in 2021. Cheers!

Re: Change of Cassandra TTL

That's an awesome tool! I forgot that it's included in https://cassandra.apache.org/_/ecosystem.html.  On Thu, 30 Sept 2021 at 16:27, Stefan Miklosovic < stefan.mikloso...@instaclustr.com> wrote: > Hi Raman, > > we at Instaclustr have created a CLI tool (1) which can strip TTLs > from your

Re: COUNTER timeout

The obvious conclusion is to say that the nodes can't keep up so it would be interesting to know how often you're issuing the counter updates. Also, how are the commit log disks performing on the nodes? If you have monitoring in place, check the IO stats/metrics. And finally, review the logs on

Re: Change of Cassandra TTL

You'll need to write an ETL app (most common case is with Spark) to scan through the existing data and update it with a new TTL. You'll need to make sure that the ETL job is throttled down so it doesn't overload your production cluster. Cheers! >

Re: hints for a node that was removed from cluster

Hints for a removed node should have been dropped. Out of curiosity, how do you know they belong to the removed node?

Re: Question related to nodetool repair options

No, I'm just saying that [-pr] is the same as [-pr -full], NOT the same as just [-full] on its own. Primary range repairs are not compatible with incremental repairs so by definition, -pr is a [-pr -full] repair. I think you're confusing the concept of a full repair vs incremental. This document

Re: Question related to nodetool repair options

1. Will perform a full repair vs incremental which is the default in some later versions. 2. As you said, will only repair the token range(s) on the node for which it is a primary owner. 3. The -full flag with -pr is redundant -- primary range repairs are always done as a full

Re: Migrating Cassandra from 3.11.11 to 4.0.0 vs num_tokens

It isn't possible to change the tokens on a node once it is already part of the cluster. Cassandra won't allow you to do it because it will make the data already on disk unreadable. You'll need to either configure new nodes or add a new DC. I've answered an identical question in

Re: Looking for pointers about replication internal working

In the interest of you not getting any responses, I'm not personally aware if such references exist. That's not to say they don't but I just don't know about them because that was a long time ago and it was before my time. If you don't get any other responses, perhaps you could search through the

Re: Large number of tiny sstables flushed constantly

4 flush writers isn't bad since the default is 2. It doesn't make a difference if you have fast disks (like NVMe SSDs) because only 1 thread gets used. But if flushes are slow, the work gets distributed to 4 flush writers so you end up with smaller flush sizes although it's difficult to tell how

Re: nodetool listsnapshots and auto snapshots from dropped tables

Awesome! Thanks, mate!  >

Re: New Servers - Cassandra 4

That's 430TB of eggs in the one 4U basket so consider that against your MTTR requirements. I fully understand the motivation for that kind of configuration but *personally*, I wouldn't want to be responsible for its day-to-day operation but maybe that's just me. 

Re: Large number of tiny sstables flushed constantly

Is it possible that you've got memtable_cleanup_threshold set in cassandra.yaml with a low value? It's been deprecated in C* 3.10 ( CASSANDRA-12228 ). If you do have it configured, I'd recommend removing it completely and restart C* when you

Re: nodetool listsnapshots and auto snapshots from dropped tables

Dropped tables used to be handled differently and were no longer tracked once they were dropped. The clearsnapshot command was fixed (CASSANDRA-6418 ) but listsnapshots doesn't appear to be (for whatever reason). It looks like an oversight to

Re: Validation of NetworkTopologyStrategy data center name in Cassandra 4.0

You are correct. Cassandra no longer allows invalid DC names for NetworkTopologyStrategy in CREATE KEYSPACE or ALTER KEYSPACE from 4.0 ( CASSANDRA-12681 ). FWIW, here is the NEWS.txt

Re: WARN on free space across data volumes (false positive)

Out of curiosity, does that mean that your `data_file_directories` is different to `storageDir`?

Re: WARN on free space across data volumes (false positive)

I'd say that your `data_file_directories` is pointing at /var/lib/cassandra/data and is mounted on the root volume instead of /srv/var. Cheers!

Re: Issue with native protocol

Then that's the cause for the node negotiating down to an older protocol version by design for dealing with mixed-version clusters as Sam described in his response. As Bowen stated, you must have had an old node back from when it was still a C* 2.2 cluster that you probably tried to

Re: Issue with native protocol

Is 10.39.36.152 part of the cluster or is it dead? >

Re: Issue with native protocol

Thanks, Pekka. But we know from an earlier post from Srinivas that the driver is trying to negotiate with v4 but the node wouldn't: [2021-07-09 23:26:52.382 -0700] com.datastax.driver.core.Connection - DEBUG: Got unsupported protocol version error from /: for version V4 server supports version

Re: Issue with native protocol

When you restart C*, you should have an entry in the logs which look like this that indicates it defaults to v4: INFO [main] 2021-07-28 20:45:31,178 StorageService.java:650 - Native protocol supported versions: 3/v3, 4/v4, 5/v5-beta (default: 4/v4) I'm hoping someone else here on the mailing

Re: High memory usage during nodetool repair

Based on the symptoms you described, it's most likely caused by SSTables being mmap()ed as part of the repairs. Set `disk_access_mode: mmap_index_only` so only index files get mapped and not the data files. I've explained it in a bit more detail in this article --

Re: Issue with native protocol

Someone asked me about the same issue a couple of months ago and we never managed to figure out why the wrong version is being displayed. Could you try to run `SELECT native_protocol_version FROM system.local`? It should come back with 4. Cheers!

Re: cassandra 4.0 java 11 support

There's been some discussion around removing the "experimental" tag for C* 4.0 + Java 11 so by all means, we encourage everyone to try it and report back to the community if you run into issues. Java 11 support was added 2 years ago so I think most of the issues have been ironed out. Now that 4.0

Re: Permission/Role Cache causing timeouts in apps.

Are you using the default `cassandra` superuser role? Because that would be expensive. Also confirm if you've set the replication for the `system_auth` keyspace to NTS because if you have multiple DCs, the request could be going to another DC. It's interesting that you've set validity to over 3

Re: R/W timeouts VS number of tables in keyspace

I wanted to add a word of warning that switching to G1 won't necessarily give you breathing space. In fact, I know it definitely won't. In your original post, it looked like the node had a very small heap (2GB). In my experience, you need to allocate at least 8GB of memory to the heap for

Re: Adding new DC

I wouldn't use either of the steps you outlined. Neither of them are correct. Follow the procedure documented here instead -- https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/operations/opsAddDCToCluster.html. Cheers!

Re: Number of DCs in Cassandra

You can really have as many as you need. The most unusual clusters I've worked on had about 12 DCs mostly because they had different workloads that needed to be isolated into their own DCs so one workload didn't affect another. FWIW by "workloads" I mean OLTP, analytics, reporting, etc. How many

Re: TWCS repair and compact help

You definitely shouldn't perform manual compactions -- you should let the normal compaction tasks take care of it. It is unnecessary to manually run compactions since it creates more problems than it solves as I've explained in this post -- https://community.datastax.com/questions/6396/. Cheers!

Re: Cassandra-stress tool creating Static columns in COMPACT STORAGE Table

Noting here that this was already answered by Benjamin on the dev ML here [1]. Cheers! [1] https://lists.apache.org/thread.html/rf9c74e8e3d431ff395f73677a616a9fcd70a46f3ea0500b71ca4d91d%40%3Cdev.cassandra.apache.org%3E >

Re: On-prem backup options ... Medusa?

There are a lot of companies who use Medusa in production, yes. Archiving to NFS is a good option and works in a lot of use cases. You'd just want to make sure that there's limited access to the backups so they can't be accidentally deleted or result in a security breach. We would love to hear

Re: Turn off automatic granting

There's definitely a case for separation of duties. For example, admin roles who have DDL permissions should not have DML access. To achieve this, you'll need to manage the permissions at a granular level and revoke permissions from the role. Cheers! >

Re: multiple clients making schema changes at once

:41, Erick Ramirez wrote: > I wonder if there’s a way to query the driver to see if your schema change >> has fully propagated. I haven’t looked into this. >> > > Yes, the drivers have APIs for this. For example, the Java driver has > isSchemaInAgreement() and checkSc

Re: multiple clients making schema changes at once

> > I wonder if there’s a way to query the driver to see if your schema change > has fully propagated. I haven’t looked into this. > Yes, the drivers have APIs for this. For example, the Java driver has isSchemaInAgreement() and checkSchemaAgreement(). See

Re: Memory requirements for Cassandra reaper

2GB is allocated to the Reaper JVM on startup (see https://github.com/thelastpickle/cassandra-reaper/blob/2.2.4/src/packaging/bin/cassandra-reaper#L90-L91 ). If you just want to test it out on a machine with only 8GB, you can update the cassandra-reaper script to only use 1GB by setting -Xms1G

Re: V3.11.10 Docker uses Java 1.8-282, why not Java 3.11

There are lots of vendors who will continue to support Java 8 given it's LTS until 2024(?). Discussion has started around officially supporting Java 11 for 4.x but that won't happen until after 4.0 GA. We encourage everyone in the community to actively test C* 4.0 with Java 11 so it becomes a

Re: io.netty.channel.unix.Errors$NativeIoException: Connection reset by peer

That message gets logged when the node tries to respond back to the client but the driver has already given up waiting for the cluster to respond so the connection is no longer active. It typically happens when running an expensive query and the coordinator is still waiting for the replicas to

Re: Datastax Java Driver Compatibility Matrix

> > Is there a Datastax Java Driver > > Compatibility matrix available for Cassandra 4.0? > No, there isn't but the same driver versions apply to C* 4.0 under the column 3.0+. Thanks for bringing this up as it has

Re: New open-source CQL driver for Rust released - 0.1.0

Thanks, Piotr & team. Fantastic contribution! I'll request Constantia.io to get in contact with you to shortlist it in next month's Changelog blog post. Cheers!

Re: Log Rotation of Extended Compaction Logging

As far as I'm aware, the compaction logs don't get rotated. It looks like it just increments the sequence number by 1. You can have a look at the logic here -- https://github.com/apache/cassandra/blob/cassandra-3.11.6/src/java/org/apache/cassandra/db/compaction/CompactionLogger.java#L303-L318.

Re: Backup cassandra and restore. Best practices

Minio is a supported type -- https://github.com/apache/libcloud/blob/trunk/libcloud/storage/types.py#L108 On Tue, 6 Apr 2021 at 20:29, Erick Ramirez wrote: > This is a useful tool, but we look for smth that could store backups in >> local S3 (like minio), not Amazon or else.. >>

Re: Backup cassandra and restore. Best practices

> > This is a useful tool, but we look for smth that could store backups in > local S3 (like minio), not Amazon or else.. > As I stated in my response, Medusa supports any S3-like storage that the Apache Libcloud API can access. See the docs I linked. Cheers!

Re: Backup cassandra and restore. Best practices

I'd recommend using Medusa ( https://github.com/thelastpickle/cassandra-medusa/wiki) -- an open-source tool which automates backups and has support for archiving to S3, Google Cloud and any S3-like storage. Cheers! >

Re: Ansible Cassandra Collection

Fantastic, Rhys! Thanks very much. I'm sure it will prove very useful for users in the community. Cheers! >

Re: Barman equivalent for Cassandra?

I'm not familiar with Barman but if you're looking for a backup software for Cassandra, have a look at Medusa from The Last Pickle -- https://github.com/thelastpickle/cassandra-medusa/wiki. It's open-source and is also used for https://k8ssandra.io/ -- the platform for deploying Cassandra on

Re: No node was available to execute query error

Does it get returned by the driver every single time? The NoNodeAvailableException gets thrown when (1) all nodes are down, or (2) all the contact points are invalid from the driver's perspective. Is it possible there's no route/connectivity from your app server(s) to the 172.16.x.x network? If

Re: underutilized servers

The tpstats you posted show that the node is dropping reads and writes which means that your disk can't keep up with the load meaning your disk is the bottleneck. If you haven't already, place data and commitlog on separate disks so they're not competing for the same IO bandwidth. Note that It's

Re: MISSING keyspace

The timestamp (1614575293790) in the snapshot directory name is equivalent to 1 March 16:08 GMT: actually I found a lot of .db files in the following directory: > > /var/lib/cassandra/data/mykespace/mytable-2795c0204a2d11e9aba361828766468f/snapshots/dropped-1614575293790- > mytable > which lines

Re: Cassandra on arm aws instances

> > it's not the same, notice I wrote r6gd, these are the ones with nvme, i'm > looking just at those. > I'm aware. I did use r6gd.2xlarge in my example. :) > I do not need all the space that i3en gives me (and probably won't be able > to use it all due to memory usage, or have other issues

Re: Cassandra on arm aws instances

The instance types you refer to are contradictory so I'm not really sure if this is really about Arm-based servers. The i3en-vs-r6 is not an apples-for-apples comparison. The R6g type is EBS-only so they will perform significantly worse than i3 instances. R6gd come with NVMe SSDs but they are

Re: MISSING keyspace

As the warning message suggests, you need to check for schema disagreement. My suspicion is that someone made a schema change and possibly dropped the problematic keyspace. FWIW I suspect the keyspace was dropped because the table isn't new -- CF ID cba90a70-5c46-11e9-9e36-f54fe3235e69 is

  1   2   3   4   >