So, my experiment didn't quite work out.
I was hoping to use G1 collector to minimize pauses -- pauses didn't
really go away, but what's worse is I think the memtable memory
calculations are driven by CMS, so my memtables would fill up and cause
Cass to run out of heap :(
On 2012-09-09 19:0
Starting with 1.6.0_34, you'll need xss set to 180k. It's updated with the
forthcoming 1.1.5 as well as the next minor rev of 1.0.x (1.0.12).
https://issues.apache.org/jira/browse/CASSANDRA-4631
See also the comments on https://issues.apache.org/jira/browse/CASSANDRA-4602
for the reference to wh
This is necessary under the later versions of 1.6v35 as well. Nodetool will
show the cluster as being down even though individual nodes will be up.
--Chris
On Sep 9, 2012, at 7:13 AM, dong.yajun wrote:
> ruuning for a while, you should set the -Xss to more than 160k when you using
> jdk1.7.
@dong, any reason to do so??
On Sun, Sep 9, 2012 at 4:43 PM, dong.yajun wrote:
> ruuning for a while, you should set the -Xss to more than 160k when you
> using jdk1.7.
>
>
> On Sun, Sep 9, 2012 at 3:39 AM, Peter Schuller <
> peter.schul...@infidyne.com> wrote:
>
>> > Has anyone tried running 1.
ruuning for a while, you should set the -Xss to more than 160k when you
using jdk1.7.
On Sun, Sep 9, 2012 at 3:39 AM, Peter Schuller
wrote:
> > Has anyone tried running 1.1.1 on Java 7?
>
> Have been running jdk 1.7 on several clusters on 1.1 for a while now.
>
> --
> / Peter Schuller (@scode, ht
> Has anyone tried running 1.1.1 on Java 7?
Have been running jdk 1.7 on several clusters on 1.1 for a while now.
--
/ Peter Schuller (@scode, http://worldmodscode.wordpress.com)
Has anyone tried running 1.1.1 on Java 7?
I know Datastax does not recommend it for DSE, is there a reason why ?
Regards,
Oleg
