Attached log and conf file to
https://issues.apache.org/jira/browse/CASSANDRA-924. Thanks.
On Sat, Mar 27, 2010 at 2:43 PM, Stu Hood stu.h...@rackspace.com wrote:
Could you try running your experiment again with DEBUG logging enabled, and
then attaching the logs to a JIRA?
-Original
Hi, I have a question about Cassandra's data model I was hoping you guys could
help me with. Most of our queries are performed against a series of tables
containing crypto keys and their associated meta data. A key could have any
number of identifiable attributes that need to be searchable:
On Fri, Mar 26, 2010 at 14:47, Jonathan Ellis jbel...@gmail.com wrote:
On Fri, Mar 26, 2010 at 7:40 AM, Henrik Schröder skro...@gmail.com
wrote:
For each indexvalue we insert a row where the key is indexid + : +
indexvalue encoded as hex string, and the row contains only one column,
where
On Mon, Mar 29, 2010 at 4:06 AM, Henrik Schröder skro...@gmail.com wrote:
On Fri, Mar 26, 2010 at 14:47, Jonathan Ellis jbel...@gmail.com wrote:
It's a unique index then? And you're trying to read things ordered by
the index, not just give me keys with that have a column with this
value?
So, what does anti-entropy repair do then?
Sounds like you have to 'decommission' the dead node, then I thought run
'nodeprobe repair' to get the data adjusted back to a replication factor of
3, right?
Also, what is the method to decommission a dead node? pass in the IP address
of the dead node
On Mon, Mar 29, 2010 at 10:31 AM, Matthew Stump mrevilgn...@gmail.com wrote:
Am I crazy to want to switch our server's primary data store from postgres to
cassandra? This is a system used by banks and governments to store crypto
keys which absolutely can not be lost.
What benefits would you
On Wed, Mar 24, 2010 at 5:07 PM, Peter Chang pete...@gmail.com wrote:
Hector is the way to go if you're using java. I'm using it right now and
it's made things worlds easier.
The reason why it wasn't bundled was because it's a separate and relatively
new project. I think it's under a month old
On Mar 29, 2010, at 12:40 PM, Eric Hauser wrote:
BTW, does anyone from Digg patrol the list? I'm really interested in some
additional the implementation of atomic counters with ZooKeeper.
I know at least three Diggers patrol the list and one of them is a committer to
Cassandra. Last I
On Mon, Mar 29, 2010 at 2:41 PM, Joe Stump j...@joestump.net wrote:
I know at least three Diggers patrol the list and one of them is a committer
to Cassandra. Last I heard from my former coworkers at Digg was that
ZooKeeper can be more overhead than wanted when doing locks in a high write
Are writes on OrderPreservingPartitioner always slower than RandomPartitioner?
Is the replication factor a 'factor' in the write times?
Thanks,
Carlos
This email message and any attachments are for the sole use of the intended
recipients and may contain proprietary and/or confidential
OPP should only affect write speed if OPP's tendency to unevenly distribute
load causes some nodes to be overworked.
In other words, OPP vs. RP on a single node system should have no real effect.
-Original Message-
From: Carlos Sanchez carlos.sanc...@riskmetrics.com
Date: Mon, 29 Mar
On Fri, Mar 26, 2010 at 4:35 PM, Mike Malone m...@simplegeo.com wrote:
With the random partitioner there's no need to suggest a token. The key
space is statistically random so you should be able to just split 2^128 into
equal sized segments and get fairly equal storage load. Your read / write
12 matches
Mail list logo