On 2012.07.18. 7:13, Code Box wrote:
The cassandra stress tool gives me values around 2.5 milli seconds for
writing. The problem with the Cassandra Stress Tool is that it just
gives the average latency numbers and the average latency numbers that
i am getting are comparable in some cases. It
Thank you for the mail. Same here, but I restarted the affected server
before I noticed your mail.
It affected both OpenJDK Java 6 (packaged with Ubuntu 10.04) and Oracle
Java 7 processes. Ubuntu 32 bit servers had no issues, only a 64 bit
machine.
Likely it is related to the leap second
You have to use PropertyFileSnitch and NetworkTopologyStrategy to
create a multi-datacenter setup with two circles. You can start
reading from this page:
http://www.datastax.com/docs/1.0/cluster_architecture/replication#about-replica-placement-strategy
Moreover all
I am thinking about the frequent example:
dc1 - node1: 0
dc1 - node2: large...number
dc2 - node1: 1
dc2 - node2: large...number + 1
In theory using the same tokens in dc2 as in dc1 does not significantly
affect key distribution, specifically the two keys on the border will
move to the next
For Cassandra testing I am using a very old server with a one core
Celeron processor and 1GiB RAM, and another one with 4GiB and 4 cores,
both with two consumer SATA hard disks. Both works, i.e. there is no out
of memory error etc. There are about 10 writes and reads per second,
maybe more,
* Does the column name get stored for every col/val for every key
(which sort of worries me for long column names)
Yes, the column name is stored with each value for every key, but it may
not matter if you switch on compression, which AFAIK has only advantages
and will be the default. I
I have played with a test cluster, stopping cassandra on one node and
updating a row on another. I noticed a delay in delivering hinted
handoffs for which I don't know the rationale. After the node which
originally received the update noticed that the other server is up, it
waited 16 s before
I noticed a strange phenomenon with Cassandra, and I would like to know
if this is something completely impossible, or not.
As you can see in the log extract below, as new versions of a row is
written out, the reads returns obsolete data after a while (they read
version 78 when 79 and even 80
József Levente wrote:
I noticed a strange phenomenon with Cassandra, and I would like to
know if this is something completely impossible, or not.
As you can see in the log extract below, as new versions of a row is
written out, the reads returns obsolete data after a while (they read
version 78
