Re: Re: Request Timeout with Composite Columns and CQL3

On Thu, Jun 28, 2012 at 6:43 PM, Henning Kropp wrote: > I would like to use the BulkOutputFormat so. Is it likely to cause the below > exception? If so, why? Can it be fixed? It could, and if that only happens when you use it, then there is a good change this is where there is a problem. But I'll

ClassCastException during Cassandra server startup

Hello, When I start the Cassandra server, some exceptions occur: INFO 10:22:16,014 reading saved cache /var/lib/cassandra/saved_caches/apispark-CellMessage-KeyCache INFO 10:22:16,016 Opening /var/lib/cassandra/data/apispark/CellMessage/apispark-CellMessage-hd-2 (498 bytes) INFO 10:22:16,016

Question on pending tasks in compaction manager

Hi All, Could someone explain why the compaction manager stops compacting when it has a number of pending tasks? I have a test cluster that I am using to stress test IO throughput, i.e. find out what a safe load for our hardware is. Over a 16 hour period my node cluster completes approximately 49

upgrade issue

Hi, I have upgraded cassndra from 0.8.6 to 1.0.10 and found following errors once i started service; INFO 05:11:50,948 Logging initialized INFO 05:11:50,953 JVM vendor/version: OpenJDK 64-Bit Server VM/1.6.0_24 INFO 05:11:50,954 Heap size: 511705088/511705088 INFO 05:11:50,955 Classpath: /opt/a

Re: Cassandra Authentication

You can build a jar from the SimpleAuthenticator and SimpleAuthority classes found in the examples. Then put the jar on the classpath of the cassandra, nicest way is to modify the startup script: put an s with options on line 148 in bin/cassandra: args=`getopt vfhp:bD: "$@"` becomes (note the add

items removed from 1.1.0 cfstats output

Were Key cache capacity: Key cache size: Key cache hit rate: Row cache: removed from cfstats in 1.1.0? I can see them in 1.0.8 but not 1.1.0. If so, was wondering why, as they're fairly useful :) Bill

RE items removed from 1.1.0 cfstats output

These settings are global since cassandra 1.1: - Make sure that global settings: key_cache_{size_in_mb, save_period} and row_cache_{size_in_mb, save_period} in conf/cassandra.yaml are used instead of per-ColumnFamily options. https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=b

RE: upgrade issue

Replace tabs with spaces in Cassandra.yaml Best regards / Pagarbiai Viktor Jevdokimov Senior Developer Email: viktor.jevdoki...@adform.com Phone: +370 5 212 3063, Fax +370 5 261 0453 J. Jasinskio 16C, LT-01112 Vilnius, Lithuania Follow us on Twitter: @adform

Re: upgrade issue

Thanks for the help. Now I am facing another issue; INFO 09:23:45,111 Logging initialized  INFO 09:23:45,119 JVM vendor/version: OpenJDK 64-Bit Server VM/1.6.0_24  INFO 09:23:45,119 Heap size: 511705088/511705088

Re: RE items removed from 1.1.0 cfstats output

Right; thanks Romain. Bill On 29/06/12 13:07, Romain HARDOUIN wrote: These settings are global since cassandra 1.1: - Make sure that global settings: key_cache_{size_in_mb, save_period} and row_cache_{size_in_mb, save_period} in conf/cassandra.yaml are used instead of per-Column

Re: Distinct Counter Proposal for Cassandra

On 06/13/2012 01:00 PM, Yuki Morishita wrote: > The above implementation and most of the other ones (including stream-lib) > implement the optimized version of the algorithm which counts up to 10^9, so > may need some work. > > Other alternative is self-learning bitmap > (http://ect.bell-labs.c

Re: Distinct Counter Proposal for Cassandra

Well I obviously think it would be handy. If this get's proposed and end's up using stream-lib don't be shy about asking for help. On a more general note, it would be great to see the special case Counter code become more general atomic operation code. On 06/13/2012 01:15 PM, Utku Can Topçu wrot

Re: upgrade issue

commitlog_rotation_threshold_in_mb was removed in 1.0.0-beta1 (CASSANDRA-2771). Adeel Akbar a écrit sur 29/06/2012 15:24:18 : > Thanks for the help. Now I am facing another issue; > > INFO 09:23:45,111 Logging initialized > INFO 09:23:45,119 JVM vendor/version: OpenJDK 64-Bit Server VM/1.6.

Re: ClassCastException during Cassandra server startup

Hello, My problem seems to occur after a server restart. As a matter of fact, if I clean the data, create a new keyspace and and its structure with cqlsh, I can use the database correctly (both with cqlsh and a Java application with Astyanax). If I stop the server and restart it, I have my pr

Re: ClassCastException during Cassandra server startup

That was bug in 1.1.1 and fixed in https://issues.apache.org/jira/browse/CASSANDRA-4331. Workaround is deleting the key cache files for your index CFs should fix this. Yuki On Friday, June 29, 2012 at 10:02 AM, Thierry Templier wrote: > Hello, > > My problem seems to occur after a server re

Re: ClassCastException during Cassandra server startup

Thanks very much, Yuki, for your answer! Thierry That was bug in 1.1.1 and fixed in https://issues.apache.org/jira/browse/CASSANDRA-4331. Workaround is deleting the key cache files for your index CFs should fix this. Yuki

Re: key_cache_size_in_mb

You might want to show us the GC log's... if there are promotion failures, count on the objects which you can get by inspecting the heapdumps etc, I am kind of assuming stuff :) Regards, On Thu, Jun 28, 2012 at 11:01 PM, Gurpreet Singh wrote: > Vijay, > Thanks for the suggestion. > Row Key si

Re: Distinct Counter Proposal for Cassandra

Would it be possible to support this in a more general case by providing a distributed |= operator over arbitrary byte strings (like the + operator on counter columns), which would allow distributed bloom filters as well? Tim Wintle On Fri, Jun 29, 2012 at 6:31 AM, Chris Burroughs wrote: > Well

Data modeling question

I have a question on what the best way is to store the data in my schema. The data I have millions of nodes, each with a different cartesian coordinate. The keys for the nodes are hashed based on the coordinate. My search is a proximity search. I'd like to find all the nodes within a given di

Re: Data modeling question

Just read up on composite keys and what looks like future deprecation of super column families. I guess Option 2 would now be: - column family with composite key from grouping and location > e.g. > '0:0,0': { meta } > ... > '0:10,10' : { meta } > '1:10,0' : {meta} > … > '1:20, 10': {meta}