facing problem while using Erlang for Cassandra

Hi I'm new to Erlang and Cassandra. I just tried to do a simple insert and i'm getting below error. I'm using Cassandra 0.6.8 . I took the erlang library code from,http://svn.apache.org/viewvc/thrift/trunk/lib/erl . And generated thrift interfaces from the cassandra.thrift available with

Re: Would it be possible to implement query language on top of Cassandra?

See this discussion on the client library list http://www.mail-archive.com/client-...@cassandra.apache.org/msg00047.html Aaron On 5 Dec 2010, at 15:41, Joshua Partogi wrote: Hi, I am still new with cassandra and from what I know so far cassandra is based on Google BigTables model. And

Re: Replacing nodes of the cluster in 0.7.0-RC1

Since no reply came in afew days, I tried my proposed steps and it all worked fine. Just to let you know. On Sat, Dec 4, 2010 at 10:31 PM, Utku Can Topçu u...@topcu.gen.tr wrote: Hi All, I'm currently not happy with the hardware and the operating system of our 4-node cassandra cluster. I'm

index file and KeysCached

for each sstable, there is an index file, which is loaded in memory to locate a particular key's offset efficiently. and for each CF, KeysCached can be set to cache keys' location. could you pls tell me the difference between the two? I'm wondering whether it's necessary to set KeysCached for a

probability of node receiving (not be responsible for) the request

If a particular client send 5 requests to a 6-node cluster, then the probability of each node receiving(not be responsible for) the first request is 1/6. Assume that node1 received the 1st request, will node1 receive the 2nd request, the 3rd one, the 4th one and the 5th one with high

Re: index file and KeysCached

2010/12/5 魏金仙 sei_...@126.com for each sstable, there is an index file, which is loaded in memory to locate a particular key's offset efficiently. Index files are not held in memory. and for each CF, KeysCached can be set to cache keys' location. could you pls tell me the difference

Re: probability of node receiving (not be responsible for) the request

2010/12/5 魏金仙 sei_...@126.com If a particular client send 5 requests to a 6-node cluster, then the probability of each node receiving(not be responsible for) the first request is 1/6. Assuming RF=1 and RandomPartitioner. Assume that node1 received the 1st request, will node1 receive the

Re: Re: Cassandra 0.7 beta 3 outOfMemory (OOM)

I remember you have 2 CF's but what are the settings for:- memtable_flush_after_mins-memtable_throughput_in_mb-memtable_operations_in_millions-keys_cached-rows_cached-in_memory_compaction_limit_in_mbCan you do the JVM Heap Calculation here and see what it

Re: Cassandra 0.7 - Impact of row size and columns on compaction

AFAIK if the entire row can be read into memory the compaction will be faster. The in_memory_compaction_limit_in_mb setting is used to decide how big the row can be before it has to use a slower two pass process.Also my understanding is that one of the main factors for compaction is the number of

Re: Secondary index on SuperColumn Family , Casandra 0.7beta2

Thanks Jonathan Nicolas Santini

Re: Cassandra 0.7 - Impact of row size and columns on compaction

This is very useful. Thanks Aaron! -Naren On Sun, Dec 5, 2010 at 12:35 PM, Aaron Morton aa...@thelastpickle.comwrote: AFAIK if the entire row can be read into memory the compaction will be faster. The in_memory_compaction_limit_in_mb setting is used to decide how big the row can be before it