On 9/22/10 9:37 AM, Jonathan Ellis wrote:
it's easy to tell from tpstats which stage(s) are overloaded
On Wed, Sep 22, 2010 at 8:29 AM, Carl Bruecken
wrote:
With current implementation, it's impossible to tell from logs what the
message types (verb) were dropped. I read this w
With current implementation, it's impossible to tell from logs what
the message types (verb) were dropped. I read this was changed for
spamming, but I think the behavior should be configurable, either
aggregate counts of dropped messages or log individual occurrences with
the message verb.
On 9/20/10 12:47 PM, Peter Schuller wrote:
This drawback is unfortunate for systems that use time-based row keys.In
such systems, row data will generally not be fragmented very much, if at
all, but reads suffer because the assumption is that all data is fragmented.
Even further, in a re
The cassandra FAQ answers the question as to why reads are slower than
writes as follows:
http://wiki.apache.org/cassandra/FAQ#reads_slower_writes
This drawback is unfortunate for systems that use time-based row
keys.In such systems, row data will generally not be fragmented very
much,
