mail. If you have received this
message in error, please contact the sender immediately and irrevocably delete
this message and any copies.
From: Ananth Gundabattula [mailto:agundabatt...@threatmetrix.com]
Sent: Tuesday, June 18, 2013 10:31 AM
To: user@cassandra.apache.org
Subject: What is the eff
Thanks Aaron for the insight.
One quick question:
>The buffers are not pre allocated, but once they are allocated they are
>not returned. So it's only an issue if have lots of clients connecting
>and reading a lot of data.
So to understand you correctly, the buffer is allocated per client
connect
> *thrift_framed_transport_size_in_mb & thrift_max_message_length_in_mb*
This control the max size of a bugger allocated by thrift when processing
requests / responses. The buffers are not pre allocated, but once they are
allocated they are not returned. So it's only an issue if have lots of clie
We are currently running on 1.1.10 and planning to migrate to a higher
version 1.2.4.
The question pertains to tweaking all the knobs to reduce GC related issues
( we have been fighting a lot of really bad GC issues on 1.1.10 and met with
little
success all the way using 1.1.10)
Taking into cons
