Do you have a suggestion as to what could be a better fit for counters? Something that can also replicate across DCs and survive link breakdown between nodes (across DCs)? (and no, I don't need 100.00% precision (although it would be nice obviously), I just need to be "pretty close" for the values of "pretty")
On the subject of bug report -- I probably will -- but I'll wait a bit for more info here, perhaps there's some configuration or something that I just don't know about. Rob Coli wrote > On Tue, Jan 22, 2013 at 5:03 AM, Sergey Olefir < > solf.lists@ > > wrote: >> I am load-testing counter increments at the rate of about 10k per second. > > Do you need highly performant counters that count accurately, without > meaningful chance of over-count? If so, Cassandra's counters are > probably not ideal. > >> We wanted to test what happens if one node goes down, so we brought one >> node >> down in DC1 (i.e. the node that was handling half of the incoming >> writes). >> ... >> This led to a complete explosion of logs on the remaining alive node in >> DC1. > > I agree, this level of exception logging during replicateOnWrite > (which is called every time a counter is incremented) seems like a > bug. I would file a bug at the Apache JIRA. > > =Rob > > -- > =Robert Coli > AIM>ALK - > rcoli@ > YAHOO - rcoli.palominob > SKYPE - rcoli_palominodb -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/node-down-log-explosion-tp7584932p7584954.html Sent from the cassandra-u...@incubator.apache.org mailing list archive at Nabble.com.
