rning/errors like this is an indicator that you reached you
Cassandra cluster throughput.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p14299.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
behind with batches are enabled)
Hi,
How is this related to the original issue discussed in this thread? I would
recommend you to create a new one with detailed description of your use
case, issue, etc.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.
hi!
Did you resolve this problem? We have the same issue and can't do anything
with it. Yep cassandra is under high load but how we can fix it? More
cassandra nodes or more ignite nodes?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exce
Thanks Igor. Will do some more testing, and worst case switch Cassandra
versions etc and get back.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p13566.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
could also be a reason for this.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p13543.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
text:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p13542.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Could you please provide full stack trace?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Cassandra-Exception-tp13529p13540.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
