Q: The newer versions of Cassandra include extra information in the
exception, I **think** you can use that information to determine how many
machines the operation succeeded on. However I do not think that
information means you can make counters that timed out "bulletproof"
On Tue, Apr 16, 2013
If you are using Counters you need to do everything you can to avoid timeouts.
In the worse case we do not know where it has been applied. The increment is
applied on a lead and then replicated to the others, if the coordinator is not
the lead it may not know if the increments was applied at al
Sorry, not LOCAL QUORUM, I meant "ANY" quorum.
On Mon, Apr 15, 2013 at 4:12 AM, Moty Kosharovsky wrote:
> Hello,
>
> I'm running a 12 node cluser with cassandra 1.1.5 and oracle jdk 1.6.0_35.
> Our application constantly writes large updates with cql. Once in a while,
> an rpc_time will occur.
>
Hello,
I'm running a 12 node cluser with cassandra 1.1.5 and oracle jdk 1.6.0_35.
Our application constantly writes large updates with cql. Once in a while,
an rpc_time will occur.
Since a lot of the information is counters, its impossible for me to
understand if the updates complete partially on
