incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Ellis <jbel...@gmail.com>
Subject Re: Unstable cassandra - , Cannot allocate memory
Date Wed, 15 Dec 2010 13:27:07 GMT
Those would both work; the "right" answer is "get JNA working." :)

rc2 has improved JNA error reporting, upgrade to that and watch the messages
on startup, and then when try the snapshot.

On Wed, Dec 15, 2010 at 6:37 AM, Peter Schuller <peter.schuller@infidyne.com
> wrote:

> > This is a crash with Cassandra 0.7.0-beta3 but I am pretty sure I also
> have got this on a rc1 server too ( We are dropping and recreating keyspaces
> when this happens)
> >
> >
> >
> > I do have the JNA enabled but it looks like it is still calling an
> external program – presumably this would cause it to ask for the same memory
> as the parent process and hence die?
>
> Yes. Either enable overcommit in the Linux kernel, or use a
> sufficiently new cassandra with working JNA to avoid use of fork+exec
> for running ln.
>
> (I forget when the change wen in so not sure whether beta3/rc1 is
> recent enough for the ln fix.)
>
> --
> / Peter Schuller
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com

Mime
View raw message