We recently switched all our productions clusters to JDK7 off the EOL JDK6.
The one big gotcha, and this was -not- specifically a problem with the
Hadoop framework but you may have issues with your own applications or
clients is the with the Java 7 bytecode verifier which can be disabled
with
I am preparing to deploy multiple cluster / distros of Hadoop for testing /
benchmarking.
In my research I have noticed discrepancies in the version of the JDK that
various groups are using. Example: Hortonworks is suggesting JDK6u31, CDH
recommends either 6 or 7 providing you stick to some
maybe you've already seen this.
http://wiki.apache.org/hadoop/HadoopJavaVersions
On Oct 9, 2013, at 2:16 PM, SF Hadoop
sfhad...@gmail.commailto:sfhad...@gmail.com
wrote:
I am preparing to deploy multiple cluster / distros of Hadoop for testing /
benchmarking.
In my research I have noticed
I hadn't. Thank you!!! Very helpful.
Andy
On Wed, Oct 9, 2013 at 2:25 PM, Patai Sangbutsarakum
patai.sangbutsara...@turn.com wrote:
maybe you've already seen this.
http://wiki.apache.org/hadoop/HadoopJavaVersions
On Oct 9, 2013, at 2:16 PM, SF Hadoop sfhad...@gmail.com
wrote:
also keep in mind, that java 6 no longer gets public updates from
Oracle: http://www.oracle.com/technetwork/java/eol-135779.html
- André
On Wed, Oct 9, 2013 at 11:48 PM, SF Hadoop sfhad...@gmail.com wrote:
I hadn't. Thank you!!! Very helpful.
Andy
On Wed, Oct 9, 2013 at 2:25 PM, Patai
Does that mean for the new cluster, we probably try to start to aim to
test/use/deploy at java 7?
On Oct 9, 2013, at 3:05 PM, Andre Kelpe ake...@concurrentinc.com
wrote:
also keep in mind, that java 6 no longer gets public updates from
Oracle:
