--
=Robert Coli
AIMGTALK -
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-tp7584932p7584960.html
Sent from the cassandra-u...@incubator.apache.org
-down-log-explosion-tp7584932.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
On Tue, Jan 22, 2013 at 5:03 AM, Sergey Olefir solf.li...@gmail.com 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
would file a bug at the Apache JIRA.
=Rob
--
=Robert Coli
AIMGTALK -
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
On Tue, Jan 22, 2013 at 2:57 PM, Sergey Olefir solf.li...@gmail.com wrote:
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
Replication is configured as DC1:2,DC2:2 (i.e. every node holds the entire
data).
I really recommend using RF 3.
The error is the coordinator node protecting it's self.
Basically it cannot handle the volume of local writes + the writes for HH. The
number of in flight hints is greater
AIMGTALK -
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-tp7584932p7584960.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive
