Re: State of Cassandra and Java 7

2012-12-23 Thread Edward Capriolo
This what versions are supported is kinda up to you for example earlier versions of jdk now have bugs. I have a version of java 1.6.0_23 I believe that will not even start with the latest cassandra releases. Likewise people suggest not running the newest ones 1.7.0 because they have not tested it.

Re: State of Cassandra and Java 7

2012-12-23 Thread Fabrice Facorat
At Orange portails we are presently testing Cassandra 1.2.0 beta/rc with Java 7, and presnetly we have no issues 2012/12/22 Brian Tarbox : > What I saw in all cases was > a) set JAVA_HOME to java7, run program fail > b) set JAVA_HOME to java6, run program success > > I should have better notes but

Re: State of Cassandra and Java 7

2012-12-22 Thread Brian Tarbox
What I saw in all cases was a) set JAVA_HOME to java7, run program fail b) set JAVA_HOME to java6, run program success I should have better notes but I'm at a 6 person startup so working tools gets used and failing tools get deleted. Brian On Fri, Dec 21, 2012 at 3:54 PM, Bryan Talbot wrote: >

Re: State of Cassandra and Java 7

2012-12-21 Thread Bryan Talbot
Brian, did any of your issues with java 7 result in corrupting data in cassandra? We just ran into an issue after upgrading a test cluster from Cassandra 1.1.5 and Oracle JDK 1.6.0_29-b11 to Cassandra 1.1.7 and 7u10. What we saw is values in columns with validation Class=org.apache.cassandra.db.m

Re: State of Cassandra and Java 7

2012-12-17 Thread Brian Tarbox
I was using jre-7u9-linux-x64 which was the latest at the time. I'll confess that I did not file any bugs...at the time the advice from both the Cassandra and Zookeeper lists was to stay away from Java 7 (and my boss had had enough of my reporting that "*the problem was Java 7"* for me to spend a

Re: State of Cassandra and Java 7

2012-12-16 Thread Michael Kjellman
Brian- did you ever file any bugs with the issues you experienced? On Dec 16, 2012, at 6:35 AM, "Peter Lin" wrote: > I'm using > > Java(TM) SE Runtime Environment (build 1.7.0_07-b11) > Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) > > > > On Sun, Dec 16, 2012 at 4:54 AM, Sy

Re: State of Cassandra and Java 7

2012-12-16 Thread Peter Lin
I'm using Java(TM) SE Runtime Environment (build 1.7.0_07-b11) Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) On Sun, Dec 16, 2012 at 4:54 AM, Sylvain Lebresne wrote: > On Sat, Dec 15, 2012 at 7:12 PM, Michael Kjellman > wrote: >> >> What "issues" have you ran into? Actually c

Re: State of Cassandra and Java 7

2012-12-16 Thread Sylvain Lebresne
On Sat, Dec 15, 2012 at 7:12 PM, Michael Kjellman wrote: > What "issues" have you ran into? Actually curious because we push 1.1.5-7 > really hard and have no issues whatsoever. > > A related question is "which which version of java 7 did you try"? The first releases of java 7 were apparently famo

Re: State of Cassandra and Java 7

2012-12-15 Thread Michael Kjellman
What "issues" have you ran into? Actually curious because we push 1.1.5-7 really hard and have no issues whatsoever. On Dec 15, 2012, at 7:51 AM, "Brian Tarbox" mailto:tar...@cabotresearch.com>> wrote: We've reverted all machines back to Java 6 after running into numerous Java 7 issues...some

Re: State of Cassandra and Java 7

2012-12-15 Thread Brian Tarbox
We've reverted all machines back to Java 6 after running into numerous Java 7 issues...some running Cassandra, some running Zookeeper, others just general problems. I don't recall any other major language release being such a mess. On Fri, Dec 14, 2012 at 5:07 PM, Bill de hÓra wrote: > "At lea

Re: State of Cassandra and Java 7

2012-12-14 Thread Bill de hÓra
"At least that would be one way of defining "officially supported". Not quite, because, Datastax is not Apache Cassandra. "the only issue related to Java 7 that I know of is CASSANDRA-4958, but that's osx specific (I wouldn't advise using osx in production anyway) and it's not directly related

Re: State of Cassandra and Java 7

2012-12-14 Thread Peter Lin
for what it's worth, I'm running on java 7 with 1.1.x release without any problems. On Fri, Dec 14, 2012 at 2:43 PM, Drew Kutcharian wrote: > In addition, the DataStax official documentation states: "Versions earlier > than 1.6.0_19 should not be used. Java 7 is not recommended." > > http://ww

Re: State of Cassandra and Java 7

2012-12-14 Thread Drew Kutcharian
In addition, the DataStax official documentation states: "Versions earlier than 1.6.0_19 should not be used. Java 7 is not recommended." http://www.datastax.com/docs/1.1/install/install_rpm On Dec 14, 2012, at 9:42 AM, Aaron Turner wrote: > Does Datastax (or any other company) support Cassan

Re: State of Cassandra and Java 7

2012-12-14 Thread Aaron Turner
Does Datastax (or any other company) support Cassandra under Java 7? Or will they tell you to downgrade when you have some problem, because they don't support C* running on 7? At least that would be one way of defining "officially supported". On Fri, Dec 14, 2012 at 2:22 AM, Sylvain Lebresne wro

Re: State of Cassandra and Java 7

2012-12-14 Thread Sylvain Lebresne
What kind of official statement do you want? As far as I can be considered an official voice of the project, my statement is: "various people run in production with Java 7 and it seems to work". Or to answer the initial question, the only issue related to Java 7 that I know of is CASSANDRA-4958, b

Re: State of Cassandra and Java 7

2012-12-13 Thread Rob Coli
On Thu, Dec 13, 2012 at 11:43 AM, Drew Kutcharian wrote: > With Java 6 begin EOL-ed soon > (https://blogs.oracle.com/java/entry/end_of_public_updates_for), what's the > status of Cassandra's Java 7 support? Anyone using it in production? Any > outstanding *known* issues? I'd love to see an off

Re: State of Cassandra and Java 7

2012-12-13 Thread Michael Kjellman
Works just fine for us. On 12/13/12 11:43 AM, "Drew Kutcharian" wrote: >Hey Guys, > >With Java 6 begin EOL-ed soon >(https://blogs.oracle.com/java/entry/end_of_public_updates_for), what's >the status of Cassandra's Java 7 support? Anyone using it in production? >Any outstanding *known* issues? >