FAQ
Hi Himanish,

The instructions at
https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
are for users of the Parcel system introduced in CM 4.5. If you aren't
using parcels (probably not yet) then this super-simple step would not
apply to you and you need to follow the section below it which
explains how to upgrade package installations.

Let me know if this clears it up for you!
On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary wrote:
Hi,

I was following
https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

But the option "Upgrade Cluster.... " does not exist under the Actions Menu.

What may be causing this ?

--
Thanks & Regards
Himanish

--



--
Harsh J

Search Discussions

  • Himanish Kushary at Feb 28, 2013 at 1:51 pm
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at

    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you aren't
    using parcels (probably not yet) then this super-simple step would not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!
    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the Actions Menu.
    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J
  • Harsh J at Feb 28, 2013 at 2:07 pm
    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.
    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at

    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you aren't
    using parcels (probably not yet) then this super-simple step would not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <hima...@gmail.com>
    wrote:
    Hi,

    I was following

    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J
  • Himanish Kushary at Feb 28, 2013 at 4:50 pm
    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish
    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.
    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you aren't
    using parcels (probably not yet) then this super-simple step would not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <hima...@gmail.com>
    wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J


    --
    Thanks & Regards
    Himanish
  • Philip Langdale at Feb 28, 2013 at 5:23 pm
    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib at
    all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you aren't
    using parcels (probably not yet) then this super-simple step would not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <hima...@gmail.com>
    wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J


    --
    Thanks & Regards
    Himanish
  • Himanish Kushary at Feb 28, 2013 at 5:44 pm
    Thank you so much.You have been of real help.

    Though not important anymore, just wanted to clarify regarding my initial
    question "why am i not seeing the option "Upgrade Cluster.... exist under
    the Actions in CDH Manager". Did I miss any other vital step ?

    I know i am using the Parcel system as i was able to add a new host and
    deploy parcels to it successfully.

    Thanks
    - Himanish


    On Thu, Feb 28, 2013 at 12:23 PM, Philip Langdale wrote:

    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib at
    all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you aren't
    using parcels (probably not yet) then this super-simple step would not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <hima...@gmail.com>
    wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J


    --
    Thanks & Regards
    Himanish

    --
    Thanks & Regards
    Himanish
  • Jayita Bhojwani at Feb 28, 2013 at 5:47 pm
    Hi Himanish,

    The "Upgrade Cluster" under the Actions will show up if you're starting the
    upgrade from a CDH3 cluster, in which case a lot more steps are involved.

    - Jayita
    On Thu, Feb 28, 2013 at 9:44 AM, Himanish Kushary wrote:

    Thank you so much.You have been of real help.

    Though not important anymore, just wanted to clarify regarding my initial
    question "why am i not seeing the option "Upgrade Cluster.... exist under
    the Actions in CDH Manager". Did I miss any other vital step ?

    I know i am using the Parcel system as i was able to add a new host and
    deploy parcels to it successfully.

    Thanks
    - Himanish



    On Thu, Feb 28, 2013 at 12:23 PM, Philip Langdale wrote:

    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib at
    all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you
    aren't
    using parcels (probably not yet) then this super-simple step would
    not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <hima...@gmail.com
    wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free 4.5.

    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J


    --
    Thanks & Regards
    Himanish

    --
    Thanks & Regards
    Himanish
  • Himanish Kushary at Feb 28, 2013 at 6:44 pm
    Thanks Jayita.Got it now.
    On Thu, Feb 28, 2013 at 12:47 PM, Jayita Bhojwani wrote:

    Hi Himanish,

    The "Upgrade Cluster" under the Actions will show up if you're starting
    the upgrade from a CDH3 cluster, in which case a lot more steps are
    involved.

    - Jayita
    On Thu, Feb 28, 2013 at 9:44 AM, Himanish Kushary wrote:

    Thank you so much.You have been of real help.

    Though not important anymore, just wanted to clarify regarding my initial
    question "why am i not seeing the option "Upgrade Cluster.... exist under
    the Actions in CDH Manager". Did I miss any other vital step ?

    I know i am using the Parcel system as i was able to add a new host and
    deploy parcels to it successfully.

    Thanks
    - Himanish



    On Thu, Feb 28, 2013 at 12:23 PM, Philip Langdale wrote:

    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib
    at all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated the
    parcels from the CDH Manager UI. When I run the "Host Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you
    aren't
    using parcels (probably not yet) then this super-simple step would
    not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary <
    hima...@gmail.com>
    wrote:
    Hi,

    I was following
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free
    4.5.
    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J


    --
    Thanks & Regards
    Himanish

    --
    Thanks & Regards
    Himanish

    --
    Thanks & Regards
    Himanish
  • Harsh J at Mar 1, 2013 at 6:12 am
    Hi Himanish,

    Also generally speaking, a CDH3 -> CDH4 upgrade is considered major
    and requires steps such as HDFS metadata upgrades, etc. to occur,
    aside of changes for any other incompatible changes. However, between
    a minor release, such as CDH3u4->CDH3u5 or CDH 4.1.x to CDH 4.2.x are
    guaranteed not to break any compatibility (we strongly test for this)
    and are as easy to do as installing new versions and restarting
    services (Rolling restarts are now available).
    On Fri, Mar 1, 2013 at 12:14 AM, Himanish Kushary wrote:
    Thanks Jayita.Got it now.

    On Thu, Feb 28, 2013 at 12:47 PM, Jayita Bhojwani wrote:

    Hi Himanish,

    The "Upgrade Cluster" under the Actions will show up if you're starting
    the upgrade from a CDH3 cluster, in which case a lot more steps are
    involved.

    - Jayita

    On Thu, Feb 28, 2013 at 9:44 AM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Thank you so much.You have been of real help.

    Though not important anymore, just wanted to clarify regarding my initial
    question "why am i not seeing the option "Upgrade Cluster.... exist under
    the Actions in CDH Manager". Did I miss any other vital step ?

    I know i am using the Parcel system as i was able to add a new host and
    deploy parcels to it successfully.

    Thanks
    - Himanish




    On Thu, Feb 28, 2013 at 12:23 PM, Philip Langdale <philipl@cloudera.com>
    wrote:
    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib
    at all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated
    the
    parcels from the CDH Manager UI. When I run the "Host
    Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go
    into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the new
    jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive CLI
    seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at


    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you
    aren't
    using parcels (probably not yet) then this super-simple step would
    not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary
    <hima...@gmail.com>
    wrote:
    Hi,

    I was following


    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free
    4.5.

    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J



    --
    Thanks & Regards
    Himanish


    --
    Thanks & Regards
    Himanish


    --
    Thanks & Regards
    Himanish


    --
    Harsh J
  • Darren Lo at Mar 1, 2013 at 6:42 pm
    An exception to this is Hive. Hive has different major versions in CDH 4.0,
    CDH 4.1, and CDH 4.2, so be sure to carefully follow the CM upgrade guide
    and follow the relevant steps for Hive upgrade if you are using hive. You
    basically need to manually back up and upgrade the Hive Metastore Database.

    Here's the upgrade guide link again:
    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+Cloudera+Manager+4.5+Free+Edition

    Thanks,
    Darren

    On Thu, Feb 28, 2013 at 10:12 PM, Harsh J wrote:

    Hi Himanish,

    Also generally speaking, a CDH3 -> CDH4 upgrade is considered major
    and requires steps such as HDFS metadata upgrades, etc. to occur,
    aside of changes for any other incompatible changes. However, between
    a minor release, such as CDH3u4->CDH3u5 or CDH 4.1.x to CDH 4.2.x are
    guaranteed not to break any compatibility (we strongly test for this)
    and are as easy to do as installing new versions and restarting
    services (Rolling restarts are now available).
    On Fri, Mar 1, 2013 at 12:14 AM, Himanish Kushary wrote:
    Thanks Jayita.Got it now.


    On Thu, Feb 28, 2013 at 12:47 PM, Jayita Bhojwani <jayita@cloudera.com>
    wrote:
    Hi Himanish,

    The "Upgrade Cluster" under the Actions will show up if you're starting
    the upgrade from a CDH3 cluster, in which case a lot more steps are
    involved.

    - Jayita

    On Thu, Feb 28, 2013 at 9:44 AM, Himanish Kushary <himanish@gmail.com>
    wrote:
    Thank you so much.You have been of real help.

    Though not important anymore, just wanted to clarify regarding my
    initial
    question "why am i not seeing the option "Upgrade Cluster.... exist
    under
    the Actions in CDH Manager". Did I miss any other vital step ?

    I know i am using the Parcel system as i was able to add a new host and
    deploy parcels to it successfully.

    Thanks
    - Himanish




    On Thu, Feb 28, 2013 at 12:23 PM, Philip Langdale <
    philipl@cloudera.com>
    wrote:
    Hi Himanish,

    I'm glad everything seems to working correctly now. We'll get the docs
    updated - I think this step is only mentioned in the CDH3->4
    doc right now, but it applies in all cases where you're switching from
    packages to parcels.

    And as it hasn't been explicitly stated, parcels do not touch /usr/lib
    at all - this is deliberate. The contents of the parcels are isolated
    into version specific directories under /opt/cloudera/parcels, and we
    create symlinks in /usr/bin for binaries (but only if packaged
    binaries
    are not installed)

    --phil

    On 28 February 2013 08:50, Himanish Kushary wrote:

    Thanks a lot Harsh.That fixed the issue. I could not find references
    to
    removing older RPM's while switching to parcel based deployments.

    Would you mind pointing me to the right portion of the documentation
    please.I am really surprised that i missed such an important thing !!

    - Himanish

    On Thu, Feb 28, 2013 at 9:07 AM, Harsh J wrote:

    Hi Himanish,

    I think it is also mentioned in the docs, but when moving to
    parcels,
    the older RPMs must first be removed, so that the /usr/bin/ scripts
    can be properly pointed to to the parcel installed bits.

    You can remove the CDH (not CM) RPMs of hadoop/zookeeper/bigtop/etc.
    via yum remove, and then restart the CM agent on each node to have
    it
    create the proper new script symlinks for the new version.

    On Thu, Feb 28, 2013 at 7:21 PM, Himanish Kushary <
    himanish@gmail.com>
    wrote:
    Hello Harsh,

    Thanks for your reply. I have downloaded,distributed and activated
    the
    parcels from the CDH Manager UI. When I run the "Host
    Inspector"..the
    versions shown for the components is 2.0.0-cdh4.2.0.But when I go
    into the
    /usr/lib/hadoop or /usr/lib/hive i see the old(4.1.2) jars , the
    new
    jars
    are only under /opt/cloudera/parcels/CDH-4.2.0-1.cdh4.2.0.p0.10/

    So , I suspect that the upgrade was not successful.Even the Hive
    CLI
    seems
    to pick up the old jars while starting.

    What could have gone wrong ?
    On Thursday, February 28, 2013 7:18:34 AM UTC-5, Harsh J wrote:

    Hi Himanish,

    The instructions at

    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    are for users of the Parcel system introduced in CM 4.5. If you
    aren't
    using parcels (probably not yet) then this super-simple step
    would
    not
    apply to you and you need to follow the section below it which
    explains how to upgrade package installations.

    Let me know if this clears it up for you!

    On Thu, Feb 28, 2013 at 7:44 AM, Himanish Kushary
    <hima...@gmail.com>
    wrote:
    Hi,

    I was following

    https://ccp.cloudera.com/display/FREE45DOC/Upgrading+to+the+Latest+Version+of+CDH4+in+a+Cloudera+Managed+Deployment#UpgradingtotheLatestVersionofCDH4inaClouderaManagedDeployment-UpgradingtoCDH4.1.2orLaterUsingtheUpgradeWizard
    to upgrade from CDH4.1.2 to CDH4.2 using Cloudera Manager Free
    4.5.

    But the option "Upgrade Cluster.... " does not exist under the
    Actions
    Menu.

    What may be causing this ?

    --
    Thanks & Regards
    Himanish

    --



    --
    Harsh J


    --
    Harsh J



    --
    Thanks & Regards
    Himanish


    --
    Thanks & Regards
    Himanish


    --
    Thanks & Regards
    Himanish


    --
    Harsh J


    --
    Thanks,
    Darren

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedFeb 28, '13 at 12:18p
activeMar 1, '13 at 6:42p
posts10
users5
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase