One point in using several keyspaces is that replication factor is per keyspace.
If you have a part of your application which generate a lot of data
whoss can be lost (some non critical logs?), then a dedicated keyspace
with a smaller replication factor can be a good thing.
Kind regards,
thanks , that is helpful
S.
- Original Message
From: Jonathan Ellis jbel...@gmail.com
To: user@cassandra.apache.org
Sent: Fri, April 9, 2010 11:39:26 AM
Subject: Re: Worst case #iops to read a row
worst case is 2 or 3, depending on row size:
one seek to read the right row index block
Yes, one keyspace per app is the normal way to design things.
On Fri, Apr 9, 2010 at 11:17 PM, Dop Sun su...@dopsun.com wrote:
Hi, a question troubles me now: how many KeySpaces one application is better
to use?
The question is coming out since 0.6, Cassandra introduced a new API named
as
Thanks, I note it down.
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Saturday, April 10, 2010 9:10 PM
To: user@cassandra.apache.org
Subject: Re: How many KeySpace will you use in a single application?
Yes, one keyspace per app is the normal way to design
So, if my understanding is correct, in this case, the small replication factor
key space is a online back system, or BCP environment. :)
Very good one. Actually, one of the things which make me a little bit
uncomfortable is BCP: once something goes wrong, how to take it back? In the
Hi,
I'm testing out failover for 0.6.0-RC1 and seeing varied behavior in
Cassandra's ability to replay the commit log after a forced failure.
My test is this:
1) Run ./cassandra -f
2) Insert a value through the CLI and immediately force a shutdown of
cassandra after I see the Value inserted
http://wiki.apache.org/cassandra/Durability
On Sat, Apr 10, 2010 at 10:38 AM, Mark Greene green...@gmail.com wrote:
Hi,
I'm testing out failover for 0.6.0-RC1 and seeing varied behavior in
Cassandra's ability to replay the commit log after a forced failure.
My test is this:
1) Run
Ah ok. Sorry for the RTFM fail John ;-).
For my test with a single node, batch would make sense if I needed better
durability but with a cluster it's less of a concern with replication.
Thanks.
-Mark
On Sat, Apr 10, 2010 at 11:49 AM, Jonathan Ellis jbel...@gmail.com wrote:
Just want to ping this thread and let anyone interested know that I just
released version 1.1 which adds the ability to map the results of a Cascal
list (or get) into a scala object (annotated accordingly). It's pretty
simplistic at current as I developed it for my company's own internal needs,
Hi,
I tried to dig in problem and found
1) DIST_URL is pointed to
http://apache.osuosl.org/incubator/cassandra/0.6.0/apache-cassandra-0.6.0-beta2-bin.tar.gz
and it has no resource in it.( in Rakefile of Cassandra Gem)
DIST_URL =
Did you try master? We fixed this around the 7th, but haven't made a
release yet.
--
Jeff
On Sat, Apr 10, 2010 at 10:10 AM, Nirmala Agadgar nirmala...@gmail.com wrote:
Hi,
I tried to dig in problem and found
1) DIST_URL is pointed to
I have already read the API spesification. Honestly I do not understand
how to use it. Because there are not an examples.
For example I have a column like this:
UserNamePassword
usr1abc
usr2xyz
usr3opm
suppose I want query the user's password
12 matches
Mail list logo
