Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property
of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies.
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Wednesday, February 06, 2013 02:23
Subject: Re: Why do Datastax docs recommend Java 6?
Oracle now owns the sun hotspot team, which is inarguably the highest powered java vm team in the world. Its still really the epicenter of all java vm development.
Sent from my Verizon Wireless BlackBerry
Date: Tue, 5 Feb 2013 14:09:33 -0800
Subject: RE: Why do Datastax docs recommend Java 6?
Also, what is particular reason to use Oracle JDK over Open JDK? Sorry, I could not find this information online.
There have been tons of threads/convos on this.
In the early days of Java 7 it was pretty unstable and there was pretty much no convincing reason to use Java 7 over Java 6.
Now that Java 7 has stabilized and Java 6 is EOL it's a reasonable decision to use Java 7 and we do it in production with no issues to speak of.
That being said there was one potential situation we've seen as a community where bootstrapping new node was using 3x more CPU and getting significantly less
throughput. However, reproducing this consistently never happened AFAIK.
I think until more people use Java 7 in production and prove it doesn't cause any additional bugs/performance issues Datastax will update their docs. Until now
I'd say it's a safe bet to use Java 7 with Vanilla C* 1.2.1. I hope this helps!