Re: run cassandra on a small instance

> > You might also have some gains setting in_memory_compaction_limit_in_mb > to something very low to force Cassandra to use on disk compaction rather > than doing it in memory. Cool Ben.. thanks I'll add that to my config as well. Glad that helped. Thanks for reporting back! No problem, Nate

Re: run cassandra on a small instance

Glad that helped. Thanks for reporting back! On Sun, Feb 22, 2015 at 9:12 PM, Tim Dunphy wrote: > Nate, > > Definitely thank you for this advice. After leaving the new Cassandra > node running on the 2GB instance for the past couple of days, I think I've > had ample reason to report complete su

Re: run cassandra on a small instance

Agreed and good point. Just added it to mine - thanks Ben. On Sun, Feb 22, 2015 at 9:43 PM, Ben Bromhead wrote: > You might also have some gains setting in_memory_compaction_limit_in_mb to > something very low to force Cassandra to use on disk compaction rather than > doing it in memory. > > On

Re: run cassandra on a small instance

You might also have some gains setting in_memory_compaction_limit_in_mb to something very low to force Cassandra to use on disk compaction rather than doing it in memory. On 23 February 2015 at 14:12, Tim Dunphy wrote: > Nate, > > Definitely thank you for this advice. After leaving the new Cass

Re: run cassandra on a small instance

Nate, Definitely thank you for this advice. After leaving the new Cassandra node running on the 2GB instance for the past couple of days, I think I've had ample reason to report complete success in getting it stabilized on that instance! Here are the changes I've been able to make: I think mani

Re: run cassandra on a small instance

> > The most important things to note: > - don't include JNA (it needs to lock pages larger than what will be > available) > - turn down threadpools for transports > - turn compaction throughput way down > - make concurrent reads and writes very small > I have used the above run a healthy 5 node cl

Re: run cassandra on a small instance

I frequently test with multi-node vagrant-based clusters locally. The following chef attributes should give you an idea of what to turn down in cassandra.yaml and cassandra-env.sh to build a decent testing cluster: :cassandra => {'cluster_name' => 'VerifyCluster',

Re: run cassandra on a small instance

Hey guys, OK well I've experimented with this a bit, and I think at this point the problem with Cassandra crashing on the smaller instances is probably an issue with my data. Because what I've done is blown away my data directory to start fresh. And then started up Cassandra on the 2GB instance.

Re: run cassandra on a small instance

One welcome change is http://cassandra.apache.org/ actually starts displaying: "Latest release *2.1.3* (Changes ), Stable release *2.0.12* (Changes

Re: run cassandra on a small instance

On Wed, Feb 18, 2015 at 5:26 PM, Andrew wrote: > Let me know if I’m off base about this—but I feel like I see a lot of > posts that are like this (i.e., use this arbitrary version, not this other > arbitrary version). Why are releases going out if they’re “broken”? This > seems like a very conf

Re: run cassandra on a small instance

done? And if so, how can we do that? :) >>> >>> Thanks >>> Tim >>> >>> On Wed, Feb 18, 2015 at 8:39 PM, Jason Kushmaul | WDA < >>> jason.kushm...@wda.com> wrote: >>> >>>> I asked this previously when a similar message ca

Re: run cassandra on a small instance

running Cassandra on a 2GB instance? Or is this something we can all agree >>>> can be done? And if so, how can we do that? :) >>>> >>>> Thanks >>>> Tim >>>> >>>> On Wed, Feb 18, 2015 at 8:39 PM, Jason Kushmaul | WDA < >>

Re: run cassandra on a small instance

t; On Wed, Feb 18, 2015 at 8:39 PM, Jason Kushmaul | WDA < >>> jason.kushm...@wda.com> wrote: >>> >>>> I asked this previously when a similar message came through, with a >>>> similar response. >>>> >>>> >>>> >>>&g

Re: run cassandra on a small instance

ht”, in that stable=2.0, >>> development=2.1, whereas the apache site says stable is 2.1. >>> >>> “Right” in they assume latest minor version is development. Why not >>> have the apache site do the same? That’s just my lowly non-contributing >>> opin

Re: run cassandra on a small instance

ith a >>> similar response. >>> >>> >>> >>> planetcassandra seems to have it “right”, in that stable=2.0, >>> development=2.1, whereas the apache site says stable is 2.1. >>> >>> “Right” in they assume latest minor

Re: run cassandra on a small instance

nt=2.1, whereas the apache site says stable is 2.1. >> >> “Right” in they assume latest minor version is development. Why not have >> the apache site do the same? That’s just my lowly non-contributing opinion >> though. >> >> >> >> *Jason

Re: run cassandra on a small instance

t have > the apache site do the same? That’s just my lowly non-contributing opinion > though. > > > > *Jason * > > > > *From:* Andrew [mailto:redmu...@gmail.com] > *Sent:* Wednesday, February 18, 2015 8:26 PM > *To:* Robert Coli; user@cassandra.apache.org > *Sub

RE: run cassandra on a small instance

site do the same? That’s just my lowly non-contributing opinion though. Jason From: Andrew [mailto:redmu...@gmail.com] Sent: Wednesday, February 18, 2015 8:26 PM To: Robert Coli; user@cassandra.apache.org Subject: Re: run cassandra on a small instance Robert, Let me know if I’m off base about

Re: run cassandra on a small instance

Robert, Let me know if I’m off base about this—but I feel like I see a lot of posts that are like this (i.e., use this arbitrary version, not this other arbitrary version).  Why are releases going out if they’re “broken”?  This seems like a very confusing way for new (and existing) users to app

Re: run cassandra on a small instance

> > 2.1.2 is IMO broken and should not be used for any purpose. > Use 2.1.1 or 2.1.3. > https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/ > =Rob Cool man. Thanks for the info. I just upgraded to 2.1.3. We'll see how that goes. I can let you know more once it's been runnin

Re: run cassandra on a small instance

On Wed, Feb 18, 2015 at 5:09 PM, Tim Dunphy wrote: > I'm attempting to run Cassandra 2.1.2 on a smallish 2.GB ram instance > over at Digital Ocean. It's a CentOS 7 host. > 2.1.2 is IMO broken and should not be used for any purpose. Use 2.1.1 or 2.1.3. https://engineering.eventbrite.com/what-ve