Re: Sorl/DSE Spark

Evelyn, Can you please elaborate on below Spark is notorious for causing latency spikes in Cassandra which is not great if you are are sensitive to that. On Thu, 12 Apr 2018, 10:46 Evelyn Smith, wrote: > Are you building a search engine -> Solr > Are you building an analytics function -> Spark

Re: Sorl/DSE Spark

Are you building a search engine -> Solr Are you building an analytics function -> Spark I feel they are used in significantly different use cases, what are you trying to build? If it’s an analytics functionality that’s seperate from your operations functionality I’d build it in it’s own DC. Sp

Re: Latest version and Features

On 04/11/2018 06:12 PM, Carlos Rolo wrote: > > I blogged about this decision recently > here: https://blog.pythian.com/what-cassandra-version-should-i-use-2018/ s/it the fact/is the fact/ typo, and possibly not 100% correct on the statement in that sentence. There are commits since the last 2.1

Re: Latest version and Features

I was going to say the same thing, but then I remembered 3.1 == 3.0.1. There's nothing nothing that makes 3.11 a requirement, so that means 3.0.latest is the safest bet, with 3.11.2 being the one I'd personally go with also. On Wed, Apr 11, 2018 at 4:13 PM Carlos Rolo wrote: > If you are on 3.1.

Re: Latest version and Features

If you are on 3.1.0 I would move forward to 3.11.2. I blogged about this decision recently here: https://blog.pythian.com/what-cassandra-version-should-i-use-2018/ Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pyt

Sorl/DSE Spark

Hello, We are exploring on configuring Sorl/Spark. Wanted to get input on this. 1) How do we decide which one to use?2) Do we run this on a DC where there is less workload? Any other suggestion or comments are appreciated. Thank you.

Re: JVM Tuning post

Re G1GC in Java 9, yes it's the default, but we explicitly specify the collector when we start Cassandra. Regarding load testing, some folks like cassandra-stress, but personally I think second to production itself, there's nothing better than an environment running the full applications stack wit

Re: JVM Tuning post

Thank you for writing this. The post is really very helpful. One question - My understanding is GC tuning depends a lot on the read/write workload and the data size. What will be the right way to simulate the production workload on a non-production environment in cassandra world. On Wed, Apr 11,

Re: Latest version and Features

Everything is in the same document, you have a "New features" section plus an "Upgrading" one On 11 April 2018 at 17:24, Abdul Patel wrote: > Nicolas, > I do see all new features but instructions for upgrade are mentioned in > next section ..not sure if i missed it ..can you share that section?

Re: Latest version and Features

Nicolas, I do see all new features but instructions for upgrade are mentioned in next section ..not sure if i missed it ..can you share that section? On Wednesday, April 11, 2018, Abdul Patel wrote: > Thanks .this is perfect > > On Wednesday, April 11, 2018, Nicolas Guyomar > wrote: > >> Sorry,

Re: Latest version and Features

Thanks .this is perfect On Wednesday, April 11, 2018, Nicolas Guyomar wrote: > Sorry, I should have give you this link instead : > https://github.com/apache/cassandra/blob/trunk/NEWS.txt > > You'll find everything you need IMHO > > On 11 April 2018 at 17:05, Abdul Patel wrote: > >> Thanks. >> >

Re: Latest version and Features

Sorry, I should have give you this link instead : https://github.com/apache/cassandra/blob/trunk/NEWS.txt You'll find everything you need IMHO On 11 April 2018 at 17:05, Abdul Patel wrote: > Thanks. > > Is the upgrade process staright forward do we have any documentation to > upgrade? > > > On

Re: JVM Tuning post

Nice write-up. G1GC became the default garbage collection mechanism beginning in Java 9, right? On 04/11/2018 09:05 AM, Joao Serrachinha wrote: Many thanks to "The Last Pickle", also for TWCS advice's. Especially for C* new features on version 3.11.1 Regards, João On 11/04/2018 16:00, Jon Ha

Re: JVM Tuning post

Many thanks to "The Last Pickle", also for TWCS advice's. Especially for C* new features on version 3.11.1 Regards, João On 11/04/2018 16:00, Jon Haddad wrote: > Hey folks, > > We (The Last Pickle) have helped a lot of teams with JVM tuning over > the years, finally managed to write some stuff do

Re: Latest version and Features

Thanks. Is the upgrade process staright forward do we have any documentation to upgrade? On Wednesday, April 11, 2018, Jonathan Haddad wrote: > Move to the latest 3.0, or if you're feeling a little more adventurous, > 3.11.2. > > 4.0 discussion is happening now, nothing is decided. > > On Wed,

JVM Tuning post

Hey folks, We (The Last Pickle) have helped a lot of teams with JVM tuning over the years, finally managed to write some stuff down. We’re hoping the community finds it helpful. http://thelastpickle.com/blog/2018/04/11/gc-tuning.html

Re: Latest version and Features

Hi, New features can be found here : https://github.com/apache/cassandra/blob/cassandra-3.11/CHANGES.txt On 11 April 2018 at 16:51, Jonathan Haddad wrote: > Move to the latest 3.0, or if you're feeling a little more adventurous, > 3.11.2. > > 4.0 discussion is happening now, nothing is decided

Re: Latest version and Features

Move to the latest 3.0, or if you're feeling a little more adventurous, 3.11.2. 4.0 discussion is happening now, nothing is decided. On Wed, Apr 11, 2018 at 7:35 AM Abdul Patel wrote: > Hi All, > > Our company is planning for upgrading cassandra to maitain the audit > gudilines for patch cycle.

Latest version and Features

Hi All, Our company is planning for upgrading cassandra to maitain the audit gudilines for patch cycle. We are currently on 3.1.0, whats the latest stable version and what are the new features? Will it be better to wait for 4.0? Any news on what will be new features in 4.0 ?

Re: does c* 3.0 use one ring for all datacenters?

Thanks for your reply. I also think separate rings are more reasonable. So one ring for one dc is only for c* 1.x or 2.x without vnode? Check these references: https://docs.datastax.com/en/archived/cassandra/1.1/docs/initialize/token_generation.html http://www.luketillman.com/one-token-ring-to-r

RE: does c* 3.0 use one ring for all datacenters?

Hi, Each DC has the whole ring, each DC contains a copy of the same data. When you add replication to a new DC, all data is copied to the new DC. Within a DC, each range of token is 'owned' by a (primary) node (and replicas if you have RF > 1). If you add/remove a node in a DC, tokens will be

Re: Why nodetool cleanup should be run sequentially after node joined a cluster

I confirm what Christophe said. I always ran them in parallel without any problem, really. Historically it was using only one compactor and impact in my clusters have always been acceptable. Nonetheless, newer Cassandra versions allow multiple compactor to work in parallel during cleanup and this

Single Node Timeout Error and High Dropped Mutation after Upgradesstables

Hi , My Compression strategy in Production was *LZ4 Compression. *But I modified it to Deflate For compression change, we had to use *nodetool Upgradesstables *to forcefully upgrade the compression strategy on all sstables But once upgradesstabloes command completed on all the 5 nodes in the c

does c* 3.0 use one ring for all datacenters?

Hi All, I know it seems a stupid question, but I am really confused about the documents on the internet related to this topic, especially it seems that it has different answers for c* with vnodes or not. Let's assume the token range is 1-100 for the whole cluster, how does it distributed into the

hinted handoff replay for a tombstoned record

Hi, Recently I Came across this line Cassandra uses hinted handoff > > to replay the database mutations > the > node missed