RE: Gathering / Curating / Organizing Cassandra Best Practices & Patterns

If you read the email message, the first link below, you’ll see that it’s a well intending Apache Foundation board member who could not grasp how our community functioned. Apache Foundation messed up our community by the way they handled a routine inquiry, leaving no option for DataStax but to

Re: LEAK DETECTED while minor compaction

Maybe it's because of https://issues.apache.org/jira/browse/CASSANDRA-12014 We had the similar issue in 3.0.14, when the SSTable has more than about 51 million keys: https://issues.apache.org/jira/browse/CASSANDRA-13785 If you upgrade to 2.2.11+, you should be able to see the real compaction

RE: Gathering / Curating / Organizing Cassandra Best Practices & Patterns

Jon, This is considered the start of the problem: https://www.mail-archive.com/dev@cassandra.apache.org/msg09050.html That’s according to this well sourced article called “Fear of Staxit: What next for ASF’s Cassandra as biggest donor cuts back”

RE: Gathering / Curating / Organizing Cassandra Best Practices & Patterns

Hey Jon, If that was the issue the whole time, it’s a big nothing to fix. All DataStax and Apache Foundation ever had to do, and it’s really really easy, is execute a property rights sharing agreement that makes everyone comfortable and protects the parties from being controlled by the

Re: Is it possible / makes it sense to limit concurrent streaming during bootstrapping new nodes?

oh.. I'm sorry, that's my fault. Thank you for correction, Jon. While it's possible in theory, didn't figure out that 256-token nodes will get relatively more and more data with each next decom of 256-token node. Regards, Kyrill From: Jon Haddad

Re: Gathering / Curating / Organizing Cassandra Best Practices & Patterns

DataStax academy is great but no, no work needs to be or should be aligned with it. Datastax is an independent company trying to make a profit, they could yank their docs at any time. There’s a reason why we started doing the docs in-tree, there was too much of a reliance on DS documentation.

RE: Gathering / Curating / Organizing Cassandra Best Practices & Patterns

Any efforts described below should be aligned with, complement, enhance, fill in the outstanding work of DataStax Academy. Kenneth Brotman From: Kenneth Brotman [mailto:kenbrot...@yahoo.com] Sent: Saturday, February 24, 2018 10:16 AM To: 'user@cassandra.apache.org' Subject: RE:

Re: Is it possible / makes it sense to limit concurrent streaming during bootstrapping new nodes?

We don’t have this documented *anywhere* right now, I’ve created a JIRA to update the site with the relevant info on this topic: https://issues.apache.org/jira/browse/CASSANDRA-14258 > On Feb 24, 2018, at 7:44 AM, Jon Haddad

Re: Is it possible / makes it sense to limit concurrent streaming during bootstrapping new nodes?

You can’t migrate down that way. The last several nodes you have up will get completely overwhelmed, and you’ll be completely screwed. Please do not give advice like this unless you’ve actually gone through the process or at least have an understanding of how the data will be shifted. Adding

RE: Alignment and coodination between DataStax's online documentation and Apache Cassandra online documentation

Myrle, I see what you’re saying. That does make sense. From now on this thread will just be on the dev mailing list unless someone on this list wants to reply or comment elsewhere on this mailing list of course. If you see anything beyond what is being worked on, please make

Re: Is it possible / makes it sense to limit concurrent streaming during bootstrapping new nodes?

> By the way, is it possible to migrate towards to smaller token ranges? What > is the recommended way doing so? - Didn't see this question answered. I think, be easiest way to do this is to add new C* nodes with lower vnodes (8, 16 instead of default 256) then decom old nodes with

Re: Missing 3.11.X cassandra debian packages

Yes, it's a 'known issue' with the style of Debian repos management. Personally, I don't understand why all versions of except the latest one are intentionally removed from repo index. Because if we had several versions of a package in the repo, anyway 'apt-get install cassandra