You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Matthew Hillsborough <ma...@gmail.com> on 2013/05/27 02:05:36 UTC

Suggested Ruby client using Cassandra 1.2.5

Hi all,

I am interested in using Cassandra in a Ruby on Rails project.

After a quick search on GitHub, there seems to be two clients that
stick out for use with Ruby:

* https://github.com/twitter/cassandra
* https://github.com/kreynolds/cassandra-cql

The documentation I've read suggested that users of 1.2.5 should use
CQL vs Thrift in their client. That would point all signs to trying
the cassandra-cql client first since the Twitter client is Thrift
based.

My concern is that it seems the Twitter client has a larger community
and has more recent commits made to it.

I'm not entirely sure where the best place to start is; but if anyone
here works extensively with Ruby and/or Rails and can suggest a client
that DataStax and/or the community suggests to use, that would be
great.

Thank you for any and all recommendations.

Matthew.

Re: Suggested Ruby client using Cassandra 1.2.5

Posted by aaron morton <aa...@thelastpickle.com>.
Go with the twitter client that is more mature / under active development.

If you are just starting out / experimenting Thrift is fine to use, it's not going away. As you get more experience you may start to prefer CQL and by that time their may be a ruby/C driver.

Cheers
 
-----------------
Aaron Morton
Freelance Cassandra Consultant
New Zealand

@aaronmorton
http://www.thelastpickle.com

On 27/05/2013, at 12:05 PM, Matthew Hillsborough <ma...@gmail.com> wrote:

> Hi all,
> 
> I am interested in using Cassandra in a Ruby on Rails project.
> 
> After a quick search on GitHub, there seems to be two clients that
> stick out for use with Ruby:
> 
> * https://github.com/twitter/cassandra
> * https://github.com/kreynolds/cassandra-cql
> 
> The documentation I've read suggested that users of 1.2.5 should use
> CQL vs Thrift in their client. That would point all signs to trying
> the cassandra-cql client first since the Twitter client is Thrift
> based.
> 
> My concern is that it seems the Twitter client has a larger community
> and has more recent commits made to it.
> 
> I'm not entirely sure where the best place to start is; but if anyone
> here works extensively with Ruby and/or Rails and can suggest a client
> that DataStax and/or the community suggests to use, that would be
> great.
> 
> Thank you for any and all recommendations.
> 
> Matthew.


Re: Buggy JRE error

Posted by Chidambaran Subramanian <ch...@gmail.com>.
I got this error today.
INFO 11:16:08,067 Enqueuing flush of Memtable-LocationInfo@8820986(41/51
serialized/live bytes, 1 ops)
 INFO 11:16:08,068 Writing Memtable-LocationInfo@8820986(41/51
serialized/live bytes, 1 ops)
ERROR 11:16:08,077 Exception in thread Thread[COMMIT-LOG-ALLOCATOR,5,main]
java.io.IOError: java.io.IOException: Map failed
at
org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:127)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator$3.run(CommitLogAllocator.java:203)
at
org.apache.cassandra.db.commitlog.CommitLogAllocator$1.runMayThrow(CommitLogAllocator.java:95)
at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.io.IOException: Map failed
at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:803)
at
org.apache.cassandra.db.commitlog.CommitLogSegment.<init>(CommitLogSegment.java:119)
... 4 more
Caused by: java.lang.OutOfMemoryError: Map failed
at sun.nio.ch.FileChannelImpl.map0(Native Method)
at sun.nio.ch.FileChannelImpl.map(FileChannelImpl.java:800)
... 5 more
ERROR 11:16:08,082 Exception in thread
Thread[StorageServiceShutdownHook,5,main]
java.lang.NullPointerException
at org.apache.cassandra.gms.Gossiper.stop(Gossiper.java:1132)
at
org.apache.cassandra.service.StorageService$2.runMayThrow(StorageService.java:489)
at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30)
at java.lang.Thread.run(Thread.java:679)


Are the two issues related?

On Mon, May 27, 2013 at 1:50 PM, Kais Ahmed <ka...@neteck-fr.com> wrote:

> Hi chiddu,
>
> You have to configure your operating system to use the Oracle JRE instead
> of OpenJDK.
>
> http://www.datastax.com/docs/1.0/install/install_jre
>
>
>
> 2013/5/27 S Chidambaran <ch...@gmail.com>
>
>> I get these errors frequently as Cassandra starts up. I'm using the
>> official Java distribution from Ubuntu.
>>
>>
>> WARN 08:11:48,145 MemoryMeter uninitialized (jamm not specified as java
>> agent); assuming liveRatio of 10.0.  Usually this means cassandra-env.sh
>> disabled jamm because you are using a buggy JRE; upgrade to the Sun JRE
>> instead
>>
>>
>>
>> java version "1.6.0_27"
>> OpenJDK Runtime Environment (IcedTea6 1.12.5)
>> (6b27-1.12.5-0ubuntu0.12.04.1)
>> OpenJDK Server VM (build 20.0-b12, mixed mode)
>>
>>
>> Any idea on how to fix this?
>>
>> Regards
>> Chiddu
>>
>>
>>
>

Re: Buggy JRE error

Posted by Kais Ahmed <ka...@neteck-fr.com>.
Hi chiddu,

You have to configure your operating system to use the Oracle JRE instead
of OpenJDK.

http://www.datastax.com/docs/1.0/install/install_jre



2013/5/27 S Chidambaran <ch...@gmail.com>

> I get these errors frequently as Cassandra starts up. I'm using the
> official Java distribution from Ubuntu.
>
>
> WARN 08:11:48,145 MemoryMeter uninitialized (jamm not specified as java
> agent); assuming liveRatio of 10.0.  Usually this means cassandra-env.sh
> disabled jamm because you are using a buggy JRE; upgrade to the Sun JRE
> instead
>
>
>
> java version "1.6.0_27"
> OpenJDK Runtime Environment (IcedTea6 1.12.5)
> (6b27-1.12.5-0ubuntu0.12.04.1)
> OpenJDK Server VM (build 20.0-b12, mixed mode)
>
>
> Any idea on how to fix this?
>
> Regards
> Chiddu
>
>
>

Buggy JRE error

Posted by S Chidambaran <ch...@gmail.com>.
I get these errors frequently as Cassandra starts up. I'm using the 
official Java distribution from Ubuntu.


WARN 08:11:48,145 MemoryMeter uninitialized (jamm not specified as java 
agent); assuming liveRatio of 10.0.  Usually this means cassandra-env.sh 
disabled jamm because you are using a buggy JRE; upgrade to the Sun JRE 
instead



java version "1.6.0_27"
OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27-1.12.5-0ubuntu0.12.04.1)
OpenJDK Server VM (build 20.0-b12, mixed mode)


Any idea on how to fix this?

Regards
Chiddu