Re: Why do Datastax docs recommend Java 6?

[Shahryar Sedghi]

I use IBM JVM 7, it is free,  and for VMs over 8 GB it has a garbage
collection policy that makes it almost pause-less. We also use some
security libraries that eliminates use of other libs that you need for
Oracle.


On Thu, Apr 4, 2013 at 12:59 AM, Edward Capriolo wrote:

> Hey guys. what gives!
> Apparently Cassandra ran on 1.7 like 5 years ago. Was their a regression?
>
> jk
>
> https://github.com/jbellis/helenus
>
> Installation
> 
> * Please use jdk 1.7; Cassandra will run with 1.6 but
>   frequently core dumps on quad-core machines
> * Unpack the tar ball:
>
>
>
>
> On Wed, Feb 6, 2013 at 12:56 PM, Wei Zhu  wrote:
>
>> Anyone has first hand experience with Zing JVM which is claimed to be
>> pauseless? How do they charge, per CPU?
>>
>> Thanks
>> -Wei
>>   --
>> *From:* Edward Capriolo 
>> *To:* user@cassandra.apache.org
>> *Sent:* Wednesday, February 6, 2013 7:07 AM
>> *Subject:* Re: Why do Datastax docs recommend Java 6?
>>
>> Oracle already did this once, It was called jrockit :)
>> http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html
>>
>> Typically oracle acquires they technology and then the bits are merged
>> with the standard JVM.
>>
>> On Wed, Feb 6, 2013 at 2:13 AM, Viktor Jevdokimov <
>> viktor.jevdoki...@adform.com> wrote:
>>
>>  I would prefer Oracle to own an Azul’s Zing JVM over any other (GC) to
>> provide it for free for anyone :)
>>
>>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: @adforminsider<http://twitter.com/#!/adforminsider>
>> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
>>  [image: Adform News] <http://www.adform.com/>
>> [image: Adform awarded the Best Employer 2012]
>> <http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>
>>
>> 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:* jef...@gmail.com [mailto:jef...@gmail.com]
>> *Sent:* Wednesday, February 06, 2013 02:23
>> *To:* user@cassandra.apache.org
>> *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
>>  --
>>  *From: *"Ilya Grebnov" 
>>  *Date: *Tue, 5 Feb 2013 14:09:33 -0800
>>  *To: *
>>  *ReplyTo: *user@cassandra.apache.org
>>  *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.
>>
>> Thanks,
>> Ilya
>>  *From:* Michael Kjellman 
>> [mailto:mkjell...@barracuda.com]
>>
>> *Sent:* Tuesday, February 05, 2013 7:29 AM
>> *To:* user@cassandra.apache.org
>> *Subject:* Re: Why do Datastax docs recommend Java 6?
>>
>>  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

Re: Why do Datastax docs recommend Java 6?

[Edward Capriolo]

Hey guys. what gives!
Apparently Cassandra ran on 1.7 like 5 years ago. Was their a regression?

jk

https://github.com/jbellis/helenus

Installation

* Please use jdk 1.7; Cassandra will run with 1.6 but
  frequently core dumps on quad-core machines
* Unpack the tar ball:




On Wed, Feb 6, 2013 at 12:56 PM, Wei Zhu  wrote:

> Anyone has first hand experience with Zing JVM which is claimed to be
> pauseless? How do they charge, per CPU?
>
> Thanks
> -Wei
>   --
> *From:* Edward Capriolo 
> *To:* user@cassandra.apache.org
> *Sent:* Wednesday, February 6, 2013 7:07 AM
> *Subject:* Re: Why do Datastax docs recommend Java 6?
>
> Oracle already did this once, It was called jrockit :)
> http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html
>
> Typically oracle acquires they technology and then the bits are merged
> with the standard JVM.
>
> On Wed, Feb 6, 2013 at 2:13 AM, Viktor Jevdokimov <
> viktor.jevdoki...@adform.com> wrote:
>
>  I would prefer Oracle to own an Azul’s Zing JVM over any other (GC) to
> provide it for free for anyone :)
>
>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: @adforminsider <http://twitter.com/#!/adforminsider>
> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
>  [image: Adform News] <http://www.adform.com/>
> [image: Adform awarded the Best Employer 2012]
> <http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>
>
> 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:* jef...@gmail.com [mailto:jef...@gmail.com]
> *Sent:* Wednesday, February 06, 2013 02:23
> *To:* user@cassandra.apache.org
> *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
>  ------
>  *From: *"Ilya Grebnov" 
>  *Date: *Tue, 5 Feb 2013 14:09:33 -0800
>  *To: *
>  *ReplyTo: *user@cassandra.apache.org
>  *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.
>
> Thanks,
> Ilya
>  *From:* Michael Kjellman 
> [mailto:mkjell...@barracuda.com]
>
> *Sent:* Tuesday, February 05, 2013 7:29 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Why do Datastax docs recommend Java 6?
>
>  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!
>
>  Best,
>  Michael
>
>  *From: *Baron Schwartz 
> *Reply-To: *"user@cassandra.apache.org" 
> *Date: *Tuesday, February 5, 2013 7:21 AM
> *To: *"user@cassandra.apache.org" 
> *Subject: *Why do Datastax docs recommend Java 6?
>
>   The Datastax docs repeatedly say (e.g.
> http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not
> recommended, but they don't say why. It would be helpful to know this. Does
> anyone know?
>
>  The same documentation is referenced from the Cassandra wiki, for
> example, http://wiki.apache.org/cassandra/GettingStarted
>
>  - Baron
>
>
>
>
>
<><>

Re: Why do Datastax docs recommend Java 6?

[Peter Lin]

one thing to keep in mind with zing. on the hardware side they recommend
the following.

minimum of 6 cores
minimum of 32GB of RAM

I got an open source license of zing and plan to do some testing this month
comparing jdk6, jdk7 and zing.


On Thu, Feb 7, 2013 at 1:45 AM, Viktor Jevdokimov <
viktor.jevdoki...@adform.com> wrote:

>  A year ago they asked $10-12k per server – crazy people. With much lower
> price they could sell much more.
>
> ** **
>
> There’s no advantage for such overpriced product for Cassandra, with some
> exceptions.
>
> ** **
>
> With RF>1 it is possible for client to early timeout the request and try
> on another replica.
>
> ** **
>
> For example, for our load, Young Gen GC pauses are ~150ms every 4-5 sec
> and requirement for reads is <=40ms.
>
> With RF=4 (average local reads are <1ms), we timeout in 10ms and try form
> other replica.
>
> Requests are fulfilled by 1 node in 90%, by 2 nodes in 98%, by 3 nodes in
> >99%. SLA keeps at 99.9%, while 98% is acceptable.
>
> Sure we’d like to increase 10ms timeout on client per 1 node request
> keeping SLA >99%, but it is impossible without Zing or something else.
>
> ** **
>
> We’d like to try latest JRockit JVM, which claims a better GC performance
> than HotSpot JVM.
>
> ** **
>
> ** **
>
> ** **
>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: @adforminsider <http://twitter.com/#!/adforminsider>
> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
>  [image: Adform News] <http://www.adform.com>
> [image: Adform awarded the Best Employer 2012]
> <http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>
>
> 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:* Wei Zhu [mailto:wz1...@yahoo.com]
> *Sent:* Wednesday, February 06, 2013 19:56
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: Why do Datastax docs recommend Java 6?
>
>  ** **
>
> Anyone has first hand experience with Zing JVM which is claimed to be
> pauseless? How do they charge, per CPU?
>
> ** **
>
> Thanks
>
> -Wei
>--
>
> *From:* Edward Capriolo 
> *To:* user@cassandra.apache.org
> *Sent:* Wednesday, February 6, 2013 7:07 AM
> *Subject:* Re: Why do Datastax docs recommend Java 6?
>
> ** **
>
> Oracle already did this once, It was called jrockit :)
>
> http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html**
> **
>
> ** **
>
> Typically oracle acquires they technology and then the bits are merged
> with the standard JVM. 
>
> ** **
>
> On Wed, Feb 6, 2013 at 2:13 AM, Viktor Jevdokimov <
> viktor.jevdoki...@adform.com> wrote:
>
> I would prefer Oracle to own an Azul’s Zing JVM over any other (GC) to
> provide it for free for anyone :)
>
>  
>
> 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: @adforminsider <http://twitter.com/#!/adforminsider>
> 
>
> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
> 
>
> [image: Adform News] <http://www.adform.com/>
>
> [image: Adform awarded the Best Employer 
> 2012]<http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>
> 
>
>
> 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 i

Re: Why do Datastax docs recommend Java 6?

[Wei Zhu]

Anyone has first hand experience with Zing JVM which is claimed to be pauseless? How do they charge, per CPU?Thanks-WeiFrom: Edward Capriolo  To:
 user@cassandra.apache.org  Sent: Wednesday, February 6, 2013 7:07 AM Subject: Re: Why do Datastax docs recommend Java 6?   
Oracle already did this once, It was called jrockit :)http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html
Typically oracle acquires they technology and then the bits are merged with the standard JVM. On Wed, Feb 6, 2013 at 2:13 AM, Viktor Jevdokimov <viktor.jevdoki...@adform.com> wrote:








I would prefer Oracle to own an Azul’s Zing JVM over any other (GC) to provide it for free for anyone :)

 






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: 
@adforminsider
Take a ride with Adform's 
Rich Media Suite














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: jef...@gmail.com [mailto:jef...@gmail.com]

Sent: Wednesday, February 06, 2013 02:23
To: user@cassandra.apache.org
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





From: "Ilya Grebnov" <i...@metricshub.com>



Date: Tue, 5 Feb 2013 14:09:33 -0800


To: <user@cassandra.apache.org>


ReplyTo: user@cassandra.apache.org



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.

 
Thanks,

Ilya


From: Michael Kjellman [mailto:mkjell...@barracuda.com]

Sent: Tuesday, February 05, 2013 7:29 AM
To: user@cassandra.apache.org
Subject: Re: Why do Datastax docs recommend Java 6?


 

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!


 


Best,


Michael


 


From:
Baron Schwartz <ba...@xaprb.com>
Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
Subject: Why do Datastax docs recommend Java 6?


 




The Datastax docs repeatedly say (e.g.
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not recommended, but they don't say why. It would be helpful to know this. Does anyone know?


 


The same documentation is referenced from the Cassandra wiki, for example, http://wiki.apache.org/cassandra/GettingStarted



 


- Baron

Re: Why do Datastax docs recommend Java 6?

[Edward Capriolo]

Oracle already did this once, It was called jrockit :)
http://www.oracle.com/technetwork/middleware/jrockit/overview/index.html

Typically oracle acquires they technology and then the bits are merged with
the standard JVM.

On Wed, Feb 6, 2013 at 2:13 AM, Viktor Jevdokimov <
viktor.jevdoki...@adform.com> wrote:

>  I would prefer Oracle to own an Azul’s Zing JVM over any other (GC) to
> provide it for free for anyone :)
>
>
>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: @adforminsider <http://twitter.com/#!/adforminsider>
> Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>
>  [image: Adform News] <http://www.adform.com>
> [image: Adform awarded the Best Employer 2012]
> <http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>
>
> 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:* jef...@gmail.com [mailto:jef...@gmail.com]
> *Sent:* Wednesday, February 06, 2013 02:23
> *To:* user@cassandra.apache.org
> *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
>  ----------
>
> *From: *"Ilya Grebnov" 
>
> *Date: *Tue, 5 Feb 2013 14:09:33 -0800
>
> *To: *
>
> *ReplyTo: *user@cassandra.apache.org
>
> *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.
>
>
>
> Thanks,
>
> Ilya
>
> *From:* Michael Kjellman 
> [mailto:mkjell...@barracuda.com]
>
> *Sent:* Tuesday, February 05, 2013 7:29 AM
> *To:* user@cassandra.apache.org
> *Subject:* Re: Why do Datastax docs recommend Java 6?
>
>
>
> 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!
>
>
>
> Best,
>
> Michael
>
>
>
> *From: *Baron Schwartz 
> *Reply-To: *"user@cassandra.apache.org" 
> *Date: *Tuesday, February 5, 2013 7:21 AM
> *To: *"user@cassandra.apache.org" 
> *Subject: *Why do Datastax docs recommend Java 6?
>
>
>
> The Datastax docs repeatedly say (e.g.
> http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not
> recommended, but they don't say why. It would be helpful to know this. Does
> anyone know?
>
>
>
> The same documentation is referenced from the Cassandra wiki, for example,
> http://wiki.apache.org/cassandra/GettingStarted
>
>
>
> - Baron
>
<><>

RE: Why do Datastax docs recommend Java 6?

[Viktor Jevdokimov]

I would prefer Oracle to own an Azul's Zing JVM over any other (GC) to provide 
it for free for anyone :)

Best regards / Pagarbiai
Viktor Jevdokimov
Senior Developer

Email: viktor.jevdoki...@adform.com<mailto: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: @adforminsider<http://twitter.com/#!/adforminsider>
Take a ride with Adform's Rich Media Suite<http://vimeo.com/adform/richmedia>

[Adform News] <http://www.adform.com>
[Adform awarded the Best Employer 2012] 
<http://www.adform.com/site/blog/adform/adform-takes-top-spot-in-best-employer-survey/>


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: jef...@gmail.com [mailto:jef...@gmail.com]
Sent: Wednesday, February 06, 2013 02:23
To: user@cassandra.apache.org
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

From: "Ilya Grebnov" mailto:i...@metricshub.com>>
Date: Tue, 5 Feb 2013 14:09:33 -0800
To: mailto:user@cassandra.apache.org>>
ReplyTo: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
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.

Thanks,
Ilya
From: Michael Kjellman [mailto:mkjell...@barracuda.com]
Sent: Tuesday, February 05, 2013 7:29 AM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Why do Datastax docs recommend Java 6?

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!

Best,
Michael

From: Baron Schwartz mailto:ba...@xaprb.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
Subject: Why do Datastax docs recommend Java 6?

The Datastax docs repeatedly say (e.g. 
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not 
recommended, but they don't say why. It would be helpful to know this. Does 
anyone know?

The same documentation is referenced from the Cassandra wiki, for example, 
http://wiki.apache.org/cassandra/GettingStarted

- Baron
<><>

Re: Why do Datastax docs recommend Java 6?

[jeffpk]

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

-Original Message-
From: "Ilya Grebnov" 
Date: Tue, 5 Feb 2013 14:09:33 
To: 
Reply-To: user@cassandra.apache.org
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.

 

Thanks, 

Ilya

From: Michael Kjellman [mailto:mkjell...@barracuda.com] 
Sent: Tuesday, February 05, 2013 7:29 AM
To: user@cassandra.apache.org
Subject: Re: Why do Datastax docs recommend Java 6?

 

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!

 

Best,

Michael

 

From: Baron Schwartz 
Reply-To: "user@cassandra.apache.org" 
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org" 
Subject: Why do Datastax docs recommend Java 6?

 

The Datastax docs repeatedly say (e.g.
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not
recommended, but they don't say why. It would be helpful to know this. Does
anyone know? 

 

The same documentation is referenced from the Cassandra wiki, for example,
http://wiki.apache.org/cassandra/GettingStarted

 

- Baron

Re: Why do Datastax docs recommend Java 6?

[Michael Kjellman]

OpenJDK will be the reference JDK going forward but there are still a ton of 
differences in the way java apps work on the Oracle JDK vs the OpenJDK. Flat 
out you'll just run into weird bugs and 1.2.0 wouldn't even start with OpenJDK7

From: Ilya Grebnov mailto:i...@metricshub.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 5, 2013 2:09 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
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.

Thanks,
Ilya
From: Michael Kjellman [mailto:mkjell...@barracuda.com]
Sent: Tuesday, February 05, 2013 7:29 AM
To: user@cassandra.apache.org<mailto:user@cassandra.apache.org>
Subject: Re: Why do Datastax docs recommend Java 6?

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!

Best,
Michael

From: Baron Schwartz mailto:ba...@xaprb.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" 
mailto:user@cassandra.apache.org>>
Subject: Why do Datastax docs recommend Java 6?

The Datastax docs repeatedly say (e.g. 
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not 
recommended, but they don't say why. It would be helpful to know this. Does 
anyone know?

The same documentation is referenced from the Cassandra wiki, for example, 
http://wiki.apache.org/cassandra/GettingStarted

- Baron

RE: Why do Datastax docs recommend Java 6?

[Ilya Grebnov]

Also, what is particular reason to use Oracle JDK over Open JDK? Sorry, I
could not find this information online.

 

Thanks, 

Ilya

From: Michael Kjellman [mailto:mkjell...@barracuda.com] 
Sent: Tuesday, February 05, 2013 7:29 AM
To: user@cassandra.apache.org
Subject: Re: Why do Datastax docs recommend Java 6?

 

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!

 

Best,

Michael

 

From: Baron Schwartz 
Reply-To: "user@cassandra.apache.org" 
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org" 
Subject: Why do Datastax docs recommend Java 6?

 

The Datastax docs repeatedly say (e.g.
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not
recommended, but they don't say why. It would be helpful to know this. Does
anyone know? 

 

The same documentation is referenced from the Cassandra wiki, for example,
http://wiki.apache.org/cassandra/GettingStarted

 

- Baron

Re: Why do Datastax docs recommend Java 6?

[Michael Kjellman]

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!

Best,
Michael

From: Baron Schwartz mailto:ba...@xaprb.com>>
Reply-To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Date: Tuesday, February 5, 2013 7:21 AM
To: "user@cassandra.apache.org" 
mailto:user@cassandra.apache.org>>
Subject: Why do Datastax docs recommend Java 6?

The Datastax docs repeatedly say (e.g. 
http://www.datastax.com/docs/1.2/install/install_jre) that Java 7 is not 
recommended, but they don't say why. It would be helpful to know this. Does 
anyone know?

The same documentation is referenced from the Cassandra wiki, for example, 
http://wiki.apache.org/cassandra/GettingStarted

- Baron