See https://hudson.apache.org/hudson/job/Cassandra/543/
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.
that's your cluster's way of telling you to set up monitoring
On Wed, Sep 22, 2010 at 8:47 AM, Carl Bruecken
carl.bruec...@corp.aol.com wrote:
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
It feels like 0.7.0-beta1 is becoming too distant a spec in the
rear-view, and the delta[1] is becoming quite large. I propose we
vote to release a new beta.
SVN: https://svn.apache.org/repos/asf/cassandra/tr...@r999875
0.7.0-beta2 artifacts: http://people.apache.org/~eevans
The vote will be
On Wed, Sep 22, 2010 at 11:58 AM, Eric Evans eev...@rackspace.com wrote:
It feels like 0.7.0-beta1 is becoming too distant a spec in the
rear-view, and the delta[1] is becoming quite large. I propose we
vote to release a new beta.
SVN: