Hey Aaron,
That sounds sensible - thanks for the heads up.
Cheers,
Ben
On Dec 10, 2012, at 0:47, aaron morton wrote:
>> (and if the message is being decoded on the server site as a complete
>> message, then presumably the same resident memory consumption applies there
>> too).
> Yerp.
> An
> (and if the message is being decoded on the server site as a complete
> message, then presumably the same resident memory consumption applies there
> too).
Yerp.
And every row mutation in your batch becomes a task in the Mutation thread
pool. If one replica gets 500 row mutations from one cli
Thanks for the clarification Andrey. If that is the case, I had better ensure
that I don't put the entire contents of a very long input stream into a single
batch, since that is presumably going to cause a very large message to
accumulate on the client side (and if the message is being decoded o
Cassandra uses thrift messages to pass data to and from server. A batch is
just a convenient way to create such message. Nothing happens until you
send this message. Probably, this is what you call "close the batch".
Thank you,
Andrey
On Fri, Dec 7, 2012 at 5:34 AM, Ben Hood <0x6e6...@gmail.co
Hi,
I'd like my app to stream a large number of events into Cassandra that
originate from the same network input stream. If I create one batch mutation,
can I just keep appending events to the Cassandra batch until I'm done, or are
there some practical considerations about doing this (e.g. too
