Yeah... you can do that...

I haven't tried to mix/match different releases within a cluster, although I 
suspect I could without any problems, but I don't want to risk it.

Until we have a problem, or until we expand our clouds with a batch of new 
nodes, I like to follow the mantra... if it aint broke, don't fix it. 
(I would suggest if / when you upgrade your java that you bounce the cloud. 
Even with a rolling restart, you have to plan for it...)



> Date: Mon, 18 Jul 2011 22:54:54 -0500
> Subject: RE: Hadoop upgrade Java version
> From: jshrini...@gmail.com
> To: common-user@hadoop.apache.org
> 
> We are using Oracle JDK 6 update 26 and have not observed any problems so
> far. EA of JDK 6 update 27 is available now. We are planning to move to
> update 27 when the GA release is made available.
> 
> -Shrinivas
> On Jul 18, 2011 7:52 PM, "Michael Segel" <michael_se...@hotmail.com> wrote:
> >
> > Any release after _21 seems to work fine.
> >
> >
> >> CC: highpoint...@gmail.com; common-user@hadoop.apache.org
> >> From: john.c.st...@gmail.com
> >> Subject: Re: Hadoop upgrade Java version
> >> Date: Mon, 18 Jul 2011 19:37:02 -0600
> >> To: common-user@hadoop.apache.org
> >>
> >> We're using u26 without any problems.
> >>
> >> On Jul 18, 2011, at 4:45 PM, highpointe <highpoint...@gmail.com> wrote:
> >>
> >> > So uhm yeah. Thanks for the Informica commercial.
> >> >
> >> > Now back to my original question.
> >> >
> >> > Anyone have a suggestion on what version of Java I should be using with
> the latest Hadoop release.
> >> >
> >> > Sent from my iPhone
> >> >
> >> > On Jul 18, 2011, at 11:26 AM, high pointe <highpoint...@gmail.com>
> wrote:
> >> >
> >> >> We are in the process of upgrading to the most current version of
> Hadoop.
> >> >>
> >> >> At the same time we are in need of upgrading Java. We are currently
> running u17.
> >> >>
> >> >> I have read elsewhere that u21 or up is the best route to go.
> Currently the version is u26.
> >> >>
> >> >> Has anyone gone all the way to u26 with or without issues?
> >> >>
> >> >> Thanks for the help.
> >
                                          

Reply via email to