Re: Cassandra vs MySQL

Hi Oliver, I was in a similar situation to you and Matija a few years back as well and can vouch for what Matija has said. Some data sets are more suitable for Cassandra than others; so the answer to your question depends on the type of data and how it is modelled in Cassandra. The data model

Re: Best way to Drop Tombstones/after GC Grace

Thank you Kurt > On Mar 14, 2018, at 5:57 PM, kurt greaves wrote: > > At least set GCGS == max_hint_window_in_ms that way you don't effectively > disable hints for the table while your compaction is running. Might be > preferable to use nodetool garbagecollect if you

Re: Best way to Drop Tombstones/after GC Grace

At least set GCGS == max_hint_window_in_ms that way you don't effectively disable hints for the table while your compaction is running. Might be preferable to use nodetool garbagecollect if you don't have enough disk space for a major compaction. Also worth noting you should do a splitting major

Re: Cassandra vs MySQL

THERE ARE NO JOINS WITH CASSANDRA CQL != SQL Same for aggregation, subqueries, etc. And effectively multitable transactions are out. If you have simple single-table queries and updates, or can convert the app to do so, then you're in business. On Tue, Mar 13, 2018 at 5:02 AM, Rahul Singh

RE: [EXTERNAL] RE: What versions should the documentation support now?

I don’t think it’s acceptable to have a site that’s “just poor with holes all over, goofy examples..” The documents are a reflection of the quality standards of the group. Why would the testing of the software be any better? It sends up red flags to me Sean. I’m very concerned about whether

RE: [EXTERNAL] RE: What versions should the documentation support now?

The DataStax documentation is far superior to the Apache Cassandra attempts. Apache is just poor with holes all over, goofy examples, etc. It would take a team of people working full time to try and catch up with DataStax. I have met the DataStax team; they are doing good work. I think it would

Re: Fast Writes to Cassandra Failing Through Python Script

The problem was likely more with the fact that it can’t flush in 128ms so you backup on flush -- Jeff Jirsa > On Mar 14, 2018, at 12:07 PM, Faraz Mateen wrote: > > I was able to overcome the timeout error by setting > memtable_flush_period_in_ms to 0 for all my tables.

Re: Fast Writes to Cassandra Failing Through Python Script

I was able to overcome the timeout error by setting memtable_flush_period_in_ms to 0 for all my tables. Initially it was set to 128. Now I able to write ~4 records/min in cassandra and the script has been running for around 12 hours now. However, I am still curious that why was cassandra

Re: Best way to Drop Tombstones/after GC Grace

Can’t advise that without knowing the risk to your app if there’s data resurrected If there’s no risk, then sure - set gcgs to 0 and force / major compact if you have the room -- Jeff Jirsa > On Mar 14, 2018, at 11:47 AM, Madhu-Nosql wrote: > > Jeff, > > Thank

Re: Best way to Drop Tombstones/after GC Grace

Jeff, Thank you i got this- how about Dropping the existing Tombstones right now can setting gc_grace time to zero per Table level would be good or what would you suggest? On Wed, Mar 14, 2018 at 1:41 PM, Jeff Jirsa wrote: > What version of Cassandra? > >

Re: Best way to Drop Tombstones/after GC Grace

What version of Cassandra? https://issues.apache.org/jira/browse/CASSANDRA-7304 sort of addresses this in 2.2+ On Wed, Mar 14, 2018 at 11:32 AM, Madhu-Nosql wrote: > Rahul, > > Tomstone caused is on the Application driver side so even though they are > not using some

Re: Best way to Drop Tombstones/after GC Grace

Rahul, Tomstone caused is on the Application driver side so even though they are not using some of the Columns in their logic waht they did is that they mentioned in driver logic that means if you are updateting one Column so the rest of the Columns so the driver automatically pick some nulls,

Re: Changing a node IP address

I'll confirm that it's worked for me in the past, but you should always test changes like this in your lab/qa environment and not rely on some random person on the internet. On Wed, Mar 14, 2018 at 7:13 AM, Cyril Scetbon wrote: > And you confirm that if we use snitches

Re: Best way to Drop Tombstones/after GC Grace

Then don’t write nulls. That’s the root of the issue. Sometimes they surface from prepared statements. Othertimes they come because of default null values in objects. -- Rahul Singh rahul.si...@anant.us Anant Corporation On Mar 13, 2018, 2:18 PM -0400, Madhu-Nosql ,

Re: Changing a node IP address

And you confirm that if we use snitches like EC2Snitch or GPFS we’ll only have to update the seed list in Cassandra.yaml if this node is a seed ? — Cyril Scetbon > On Mar 13, 2018, at 10:08 PM, Jeff Jirsa wrote: > > If you're just trying to change an IP, you can just stop

Re: Migration of keyspace to another new cluster

Nate, Thank you very much for the reply, even I was trying to implement the same. Will post it after it is implemented in the above mention fashion. Thanks and Regards, Goutham Reddy Aenugu. Regards Goutham Reddy On Tue, Mar 13, 2018 at 6:40 PM, Nate McCall wrote: > >

Re: Fast Writes to Cassandra Failing Through Python Script

Thanks for the response. Here is the output of "DESCRIBE" on my table https://gist.github.com/farazmateen/1c88f6ae4fb0b9f1619a2a1b28ae58c4 I am getting two errors from the python script that I mentioned above. First one does not show any error or exception in server logs. Second error:

RE: What versions should the documentation support now?

This went nowhere quick. Come on everyone. The website has to support users who are on “supported” versions of the software. That’s more than one version. There was a JIRA on this months ago. You are smart people. I just gave a perfect answer and ended up burning a bunch of time for

Re: RE: RE: What versions should the documentation support now?

trunk is the next release which is 4.0. You won't find a branch named 4.0 yet. Dinesh On Tuesday, March 13, 2018, 11:39:44 PM PDT, Kenneth Brotman wrote: #yiv3841634821 #yiv3841634821 -- _filtered #yiv3841634821 {font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2

RE: RE: What versions should the documentation support now?

I show a 3.0 and a 3.11 branch but no 4.0. I’m at https://github.com/apache/cassandra . From: Dinesh Joshi [mailto:dinesh.jo...@yahoo.com.INVALID] Sent: Tuesday, March 13, 2018 11:30 PM To: user@cassandra.apache.org Subject: Re: RE: What versions should the documentation support now?

Re: RE: What versions should the documentation support now?

Kenneth, The only 4.x docs should go in trunk. If you would like to contribute docs to the 2.x and/or 3.x releases, please make pull requests against branches for those versions. During normal development process, the docs should be updated in trunk. When a release is cut from trunk, any

RE: What versions should the documentation support now?

I made sub directories “2_x” and “3_x” under docs and put a copy of the doc in each. No links were changed yet. We can work on the files first and discuss how we want to change the template and links. I did the pull request already. Kenneth Brotman From: Jonathan Haddad