Aaron,
Can you explain a bit when you say that the client needs to support Atomic
Batches in 1.2 and Hector doesn't support it? Does it mean that there is no
way of using atomic batch of inserts through Hector? Or did I misunderstand
you? Feel free to point me to any link or resource, thanks.
Reg
> As far as I know in 1.2 coordinator logs request before it updates replicas.
You may be thinking about atomic batches, which are enabled by default for 1.2
via CQL but must be supported by Thrift clients. I would guess Hector is not
using them.
These logs are stored on other machines, which th
Read this
http://www.datastax.com/dev/blog/atomic-batches-in-cassandra-1-2
On Tue, Jun 25, 2013 at 8:45 PM, Andrey Ilinykh wrote:
> It depends on cassandra version. As far as I know in 1.2 coordinator logs
> request before it updates replicas. If it fails it will replay log on
> startup.
> In 1
It depends on cassandra version. As far as I know in 1.2 coordinator logs
request before it updates replicas. If it fails it will replay log on
startup.
In 1.1 you may have inconsistant state, because only part of your request
is propagated to replicas.
Thank you,
Andrey
On Tue, Jun 25, 2013 a
Hi there,
I am writing data to Cassandra by thrift client (not hector) and
wonder what happen if the coordinator node fails. The same question
applies for bulk loader which uses gossip protocol instead of thrift
protocol. In my understanding, the HintedHandoff only takes care of
the replica node f
