Re: cassandra tracing's source_elapsed microseconds

> > Does the above indicate it took 20.696 milliseconds to run the last > "Partition index with 0 entries found for sstable 6" activity? > Yes, that's correct. It's cumulative. And the last entry for "Request complete" is the total time it took for the query. Cheers!

Re: best pointers to learn Cassandra maintenance

In Cassandra, "repair" refers to anti-entropy repairs. I think that's where most of the confusion is. DBAs see the word "repair" and think it is a one-off operation to "fix something broken". Users incorrectly think that once it is fixed then there shouldn't be a need to repair again. However in a

Re: sstable processing times

The operation will run in a single anti-compaction thread so it won't consume more than 1 CPU. The operation will mostly be IO-bound with the disk being the most bottleneck. Are running it on a direct-attached SSD? It won't perform well if you're running it on an EBS volume or some other slow disk.

Re: Does repair count as read/writes

Not quite. Cassandra does a validation compaction for the merkle tree calculation. And it streams SSTables instead of individual mutations from one node to another to synchronise data between replicas. Cheers!

Re: reducing RF wen using token allocation algorithm

Your approach is correct although I'd make sure that your repairs are current and successful before running cleanups. FWIW it doesn't really have anything to do with the token allocation algorithm. Cheers!

Re: migrating driver from 3.4 to 4.9

Yes, Java driver 4 is not binary-compatible with older versions. Our recommendation is that you upgrade to the latest version instead of re-coding your app for an older version. If you run into issues with the older version, you will have to upgrade anyway to get the fix. Java driver v3.4 was relea

Re: GC pauses way up after single node Cassandra 2.2 -> 3.11 binary upgrade

On Wed, 28 Oct 2020 at 14:41, Rich Hawley wrote: > unsubscribe > You need to email user-unsubscr...@cassandra.apache.org to unsubscribe from the list. Cheers!

Re: GC pauses way up after single node Cassandra 2.2 -> 3.11 binary upgrade

I haven't seen this specific behaviour in the past but things that I would look at are: - JVM options which differ between 3.11 defaults and what you have configured in 2.2 - review your monitoring and check read throughput on the upgraded node as compared to 2.2 nodes - possibly no

Re: GC pauses way up after single node Cassandra 2.2 -> 3.11 binary upgrade

> > Our JVM options are unchanged between 2.2 and 3.11 > For the sake of clarity, do you mean: (a) you're using the default JVM options in 3.11 and it's different to the options you had in 2.2? (b) you've copied the same JVM options you had in 2.2 to 3.11? The distinction is important because at

Re: SSTableloader questions

A few months ago, I was asked a similar question so I wrote instructions for this. It depends on whether the clusters are identical or not. The posts define what "identical" means. If the source and target cluster are identical in configuration, follow the procedure here -- https://community.datas

Re: Cassandra in a container - what to do (sequence of events) to snapshot the storage volume?

> > I do "nodetool flush", then snapshot the storage. Meanwhile, the DB is > under heavy read/write traffic, with lots of writes per second. What's > the worst that could happen, lose a few writes? > Nope, you won't lose anything. Snapshots in C* are the equivalent of a cold backup in relational D

Re: local read from coordinator

Yes, use a token-aware policy so the driver will pick a coordinator where the token (partition) exists. Cheers!

Re: SSTableloader questions

> > Can the sstableloader job run from outside a Cassandra node? or it has to > be run from inside Cassandra node. > Yes, I'm a fan of running sstableloader on a server that is not one of the nodes in the cluster. You can maximise the throughput by running multiple instances of sstableloader loadi

Re: Enable Ttracing

I wouldn't do it. It will significantly affect the performance of your cluster so your monitoring ends up killing the very thing it's monitoring. Perhaps you could tell us what outcome you're after so we'd be able to offer a better solution. Like audit logging, for example. Cheers! >

Re: How beta is 4.0-beta3?

The beta releases of C* 4.0 is more the equivalent of a ".0" release + bug fixes. We are grateful for the community testing it in non-production systems to identify issues so we can fix them and eventually get to a GA release soon. So by all means, please try it out and let us know how you go. Chee

Re: Vastly different disk I/O on different sized aws instances

>From C* 2.2 onwards, SSTables get mapped to memory by mmap() so the hot data will be accessed much faster on systems with more RAM. On Thu, 3 Dec 2020 at 09:57, Carl Mueller wrote: > I agree in theory, I just want some way to confirm that file accesses in > the larger instance are being interce

Re: Digest mismatch

> > Thank you Steve - once I have the key, how do I get to a node? > Run this command to determine which replicas own the partition: $ nodetool getendpoints > So if the propagation has not taken place and a node doesn't have the data > and is the first to 'be asked' the client will get no data?

Re: add javaagent MCAC (metric collector for apache cassandra) using cass-operator

Have a look at K8ssandra (https://k8ssandra.io/). It is a platform for running Apache Cassandra in Kubernetes using the DataStax Cassandra Operator (cass-operator) under the hood but with all the tooling built-in:

Re: Can you change seed nodes without doing a restart?

You just need to remove the node from it's own seeds list so it can bootstrap itself back into the cluster. Otherwise, it will immediately join the cluster without streaming data from other replicas. If you intend to promote it back as a seed node, you don't need to remove it from the seeds list o

Re: owns (effective)? Cassandra 4 b4

This appears to be the same issue reported in CASSANDRA-16273 affecting 4.0 and is currently open/unresolved. Cheers! >

Re: Snapshots space question

> > That said, the "Total TrueDiskSpaceUsed: 16.09 GiB" seems to be way off? > Or is that value something else? > It's a bit late now since you've cleared them but it would have been good to check the size of each snapshot directory with du and validate it against the listsnapshots output. FWIW sn

Re: Snapshots space question

My apologies for not being clear. What I meant was to run a du for every subdirectory in the snapshots folder and compare them with the listsnapshots output. As Kane pointed out, you might have subdirectories not listed as a snapshot. Cheers! >

Re: Understanding logging in Cassandra

You can configure which log levels get logged but you can't change the log level of the log entries. For example if an entry is logged at DEBUG level, you cannot reconfigure it to be logged at INFO since the levels are defined in the code. Also, I wouldn't disable debug logging if I were managing

Re: Understanding which table had digest mismatch

Unfortunately, you won't be able to work it out just based on that debug message. The only suggestion I have is to run repairs regularly. Cheers! >

Re: How to restore single Kubernetes node?

It really depends on how you've set up your Kubernetes cluster. For example if you're using the k8ssandra (https://k8ssandra.io/) with persistent volumes, the cass-operator should launch a new pod automatically and mount the same volume to bring the C* node back online. But it really depends on se

Re: Impact analysis of upgrading RHEL/SLES OS

In most cases, minor OS upgrades are not problematic provided you have sufficient capacity in your cluster so that it can tolerate scheduled downtime while some nodes are being upgraded. One thing you should be aware of are patches in newer versions of Linux distributions which address Spectre and

Re: Recovery after server crash 4.0b3

If the node's only been down for less than gc_grace_seconds and the data in the drives are intact, you should be fine just booting the server and it will join the cluster. You will need to run a repair so it picks up the missed mutations. @Bowen FWIW no need to do a "replace" -- the node will just

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 equivale

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 disp

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 just

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: 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 OK

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 yo

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 Kuber

Re: Ansible Cassandra Collection

Fantastic, Rhys! Thanks very much. I'm sure it will prove very useful for users in the community. 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: 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

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: 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. Che

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: 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 pro

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 res

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 know

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 and

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 https://docs.datastax.com/en/developer/

Re: multiple clients making schema changes at once

2021 at 09: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() a

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: 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 abo

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: 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: 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 d

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: 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 producti

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 da

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 i

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: 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 -- https://community.datastax.com/qu

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 lis

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 V3

Re: Issue with native protocol

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

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 remove/decommis

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: 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: 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: 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 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 ca

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: nodetool listsnapshots and auto snapshots from dropped tables

Awesome! Thanks, mate! 🍻 >

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 t

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 D

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 https://community.

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 rep

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 mi

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: 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: 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 the

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 SSTab

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: 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: 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, 2

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: 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: unsubscribe

Hey, mate. You'll need to email user-unsubscr...@cassandra.apache.org to unsubscribe from the list. 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 the

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: 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: 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: 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 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: 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 blo

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: 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 p

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: 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: 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: 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 -- th

Re: Cassandra commitlog corruption on hard shutdown

Thanks for circling back and posting your experience! >

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 interested

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

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

<    1   2   3   4   >