Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of alexandros.c.g.b@gmail.com
 designates 209.85.160.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAN0To666mDr8n_d2WC+fP2USyvMoXt=x6OWFdGmYbSD3GJ8rSQ@mail.gmail.com>
References: 
 <CAN0To666mDr8n_d2WC+fP2USyvMoXt=x6OWFdGmYbSD3GJ8rSQ@mail.gmail.com>
Date: Sun, 11 Sep 2011 14:14:24 -0500
Message-ID: 
 <CAALKmm3vEXEA65Mif9WFef5Ty6TgCf8tociO9vDrYkg0p_k50Q@mail.gmail.com>
Subject: Re: Cassandra as in-memory cache
From: =?ISO-8859-1?Q?Hern=E1n_Quevedo?= <alexandros.c.g.b@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi, all.

I=C2=B4m new at this and haven=C2=B4t been able to install cassandra in deb=
ian
6. After uncompressing the tar and creating var/log and var/lib
directories, the command bin/cassandra -f results in message "exec:
357 -ea not found" preventing cassandra from run the process README
file says it is suppose to start.

Any help would be very appreciated.

Thnx!

On 9/9/11, kapil nayar <kapilnayar1@gmail.com> wrote:
> Hi,
>
> Can we configure some column-families (or keyspaces) in Cassandra to perf=
orm
> as a pure in-memory cache?
>
> The feature should let the memtables always be in-memory (never flushed t=
o
> the disk - sstables).
> The memtable flush threshold settings of time/ memory/ operations can be =
set
> to a max value to achieve this.
>
> However, it seems uneven distribution of the keys across the nodes in the
> cluster could lead to java error no-memory available. In order to prevent
> this error can we overflow some entries to the disk?
>
> Thanks,
> Kapil
>

--=20
Sent from my mobile device

=CE=95=CE=AF=CE=BD=CE=B1=CE=B9 =CE=B7 =CE=B8=CE=AD=CE=BB=CE=B7=CF=83=CE=B7 =
=CF=84=CF=89=CE=BD =CE=98=CE=B5=CF=8E=CE=BD.