Some discussion of large data here
http://wiki.apache.org/cassandra/LargeDataSetConsiderations
When creating large rows you also need to be aware of
in_memory_compaction_limit_in_mb (see the yaml) and that all columns for a row
are stored on the same node. So if you store one file in a one row
Dne 24.9.2011 0:05, Jonathan Ellis napsal(a):
Really large messages are not encouraged because they will fragment
your heap quickly. Other than that, no.
what is recommended chunk size for storing multi gigabyte files in
cassandra? 64MB is okay or its too large?
Really large messages are not encouraged because they will fragment
your heap quickly. Other than that, no.
On Fri, Sep 23, 2011 at 3:40 PM, Sanjeev Kulkarni wrote:
> Hey guys,
> Are there any side-effects of increasing
> the thrift_framed_transport_size_in_mb and thrift_max_message_length_in_mb
Hey guys,
Are there any side-effects of increasing
the thrift_framed_transport_size_in_mb and thrift_max_message_length_in_mb
variables from their default values to something like 100mb?
Thanks!
