Re: sstableloader - warning vs. failure?

Ok, thanks very much the answer! On Fri, Feb 7, 2020 at 9:00 PM Erick Ramirez wrote: > INFO [pool-1-thread-4] 2020-02-08 01:35:37,946 NoSpamLogger.java:91 - >> Maximum memory usage reached (536870912), cannot allocate chunk of 1048576 >> > > The message gets logged when SSTables are being cache

Re: sstableloader - warning vs. failure?

> > INFO [pool-1-thread-4] 2020-02-08 01:35:37,946 NoSpamLogger.java:91 - > Maximum memory usage reached (536870912), cannot allocate chunk of 1048576 > The message gets logged when SSTables are being cached and the cache fills up faster than objects are evicted from it. Note that the message is

sstableloader - warning vs. failure?

Hi folks, When sstableloader hits a very large sstable cassandra may end up logging a message like this: INFO [pool-1-thread-4] 2020-02-08 01:35:37,946 NoSpamLogger.java:91 - Maximum memory usage reached (536870912), cannot allocate chunk of 1048576 The loading process doesn't abort, and the ss

Re: [RELEASE] Apache Cassandra 4.0-alpha3 released

Congratulations! 👏 For those who may not be familiar with the behind-the-scenes, this is a major milestone for the project and another step closer to the release of Apache Cassandra 4.0. I'm so excited about this news and you should be too! 🍻

Re: sstableloader: How much does it actually need?

Just mulling this based on some code and log digging I was doing while trying to have Reaper stay on top of our cluster. I think maybe the caveat here relates to eventual consistency. C* doesn’t do state changes as distributed transactions. The assumption here is that RF=3 is implying that at

Re: [RELEASE] Apache Cassandra 4.0-alpha3 released

Thanks for handling this, Mick! On Fri, Feb 7, 2020 at 12:02 PM Mick Semb Wever wrote: > > > The Cassandra team is pleased to announce the release of Apache Cassandra > version 4.0-alpha3. > > Apache Cassandra is a fully distributed database. It is the right choice > when you need scalability an

[RELEASE] Apache Cassandra 4.0-alpha3 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 4.0-alpha3. 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

Re: Overload because of hint pressure + MVs

There's a few things you can do here that might help. First off, if you're using the default heap settings, that's a serious problem. If you've got the head room, my recommendation is to use 16GB heap with 12 GB new gen and pin your memtable heap space to 2GB. Set your max tenuring threshold to

Re: Overload because of hint pressure + MVs

That JIRA still says Open, so no, it has not been fixed (unless there's a fixed duplicate in JIRA somewhere). For clarification, you could update that ticket with a comment including your environmental details, usage of MV, etc. I'll bump the priority up and include some possible branchX fixve

Overload because of hint pressure + MVs

Hi, We are getting hit by the below bug. Other than lowering hinted_handoff_throttle_in_kb to 100 any other work around ? https://issues.apache.org/jira/browse/CASSANDRA-13810 Any idea if it got fixed in later version. We are on Open source Cassandra 3.11.1 . Thanks Surbhi

Re: Query timeouts after Cassandra Migration

Ankit, are the instance types identical in the new cluster, with I/O configuration identical at the system level, and are the Java settings for C* identical between the two clusters? With radical timing differences happening periodically, the two things I’d have on my radar would be garbage col