Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Who agreed with this solution

avatar
author-rank Grizzly author-rank
Master Collaborator

Created ‎10-16-2013 01:08 PM

Per e-mail thread discussion 1.7 JDK was manually added before cluster upgrade, and was present within custom local yum repo at the site.

 

CM/CDH will pick the later JDK present to use.  Per Phillp L:

 

Yes. We ask yum to install jdk and if yum decides that it's appropriate to install a newer version of jdk than is already installed, that is what it will do.

 
If you want to keep a package on a particular version, even if a newer version is available in a repo, there is a way to make yum do that:
 
http://blog.serverbuddies.com/how-can-i-get-yum-to-keep-package-at-a-certain-version/
 

 

 

View solution in original post

3,915
1
Who agreed with this solution