FAQ
I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
as the major components I use. After upgrading CM 5.0 and following Upgrade
Cluster path from CM, I am stuck with the below which happens during the
start phase (after parcel activation).


Deploy Client Configuration

Command failed to run because service impala1 has invalid configuration.
Review and correct its configuration. First error: This version of CM only
supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
have taken) correct?


Any help is much appreciated.

To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Search Discussions

  • Darren Lo at Apr 15, 2014 at 5:04 pm
    Hi,

    If you click on the Hosts tab and run the Host Inspector, what does it say
    your impala version is?

    Sometimes people who are using Parcels have Impala packages of an older
    version installed, which confuses the version detection. If that's what's
    happening to you, just remove those packages.

    Thanks,
    Darren

    On Tue, Apr 15, 2014 at 9:47 AM, wrote:

    I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
    as the major components I use. After upgrading CM 5.0 and following Upgrade
    Cluster path from CM, I am stuck with the below which happens during the
    start phase (after parcel activation).


    Deploy Client Configuration

    Command failed to run because service impala1 has invalid configuration.
    Review and correct its configuration. First error: This version of CM only
    supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


    Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
    have taken) correct?


    Any help is much appreciated.

    To unsubscribe from this group and stop receiving emails from it, send an
    email to scm-users+unsubscribe@cloudera.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Skr989 at Apr 15, 2014 at 5:33 pm
    Please see the host inspector and the Impala (Add Service) screenshot.


    <https://lh5.googleusercontent.com/-2BWw_61Kr8U/U01s7g7pD_I/AAAAAAAAACU/krUwPH4jFNY/s1600/HostInspectorCM5.jpg>

    <https://lh3.googleusercontent.com/-Mr7JUwPcbpw/U01tLMN1vHI/AAAAAAAAACc/gQKBgMkOpZM/s1600/ImpalaServiceAdd_CM5.jpg>


    On Tuesday, April 15, 2014 11:47:12 AM UTC-5, skr...@gmail.com wrote:

    I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
    as the major components I use. After upgrading CM 5.0 and following Upgrade
    Cluster path from CM, I am stuck with the below which happens during the
    start phase (after parcel activation).


    Deploy Client Configuration

    Command failed to run because service impala1 has invalid configuration.
    Review and correct its configuration. First error: This version of CM only
    supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


    Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
    have taken) correct?


    Any help is much appreciated.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Skr989 at Apr 15, 2014 at 5:39 pm
    Darren,

    Thanks for the pointer. I got that fixed and I am not able to bring up
    Impala 1.3 through CM5. However, I got stuck with "impala-shell" missing
    from the command line. How would I restore it?

    -SR
    On Tuesday, April 15, 2014 11:47:12 AM UTC-5, skr...@gmail.com wrote:

    I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
    as the major components I use. After upgrading CM 5.0 and following Upgrade
    Cluster path from CM, I am stuck with the below which happens during the
    start phase (after parcel activation).


    Deploy Client Configuration

    Command failed to run because service impala1 has invalid configuration.
    Review and correct its configuration. First error: This version of CM only
    supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


    Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
    have taken) correct?


    Any help is much appreciated.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Darren Lo at Apr 15, 2014 at 6:40 pm
    Your symlinks need to be updated to point to the binaries in your parcels.
    To do this, you can either:
    1) Deactivate your CDH parcel, then re-activate it again
    2) restart your CM agents on all hosts with "service cloudera-scm-agent
    restart"

    It may take up to 5 minutes for CM to realize the binaries on your agents
    have changed, which could explain the error message. You can restart the
    agents to force them to report the new versions.

    Thanks,
    Darren

    On Tue, Apr 15, 2014 at 10:39 AM, wrote:

    Darren,

    Thanks for the pointer. I got that fixed and I am not able to bring up
    Impala 1.3 through CM5. However, I got stuck with "impala-shell" missing
    from the command line. How would I restore it?

    -SR

    On Tuesday, April 15, 2014 11:47:12 AM UTC-5, skr...@gmail.com wrote:

    I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
    as the major components I use. After upgrading CM 5.0 and following Upgrade
    Cluster path from CM, I am stuck with the below which happens during the
    start phase (after parcel activation).


    Deploy Client Configuration

    Command failed to run because service impala1 has invalid configuration.
    Review and correct its configuration. First error: This version of CM only
    supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


    Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
    have taken) correct?


    Any help is much appreciated.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to scm-users+unsubscribe@cloudera.org.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.
  • Skr989 at Apr 16, 2014 at 3:39 pm
    Thanks, Darren.

    Deactivation was not needed in my case. Agent restart fixed it.


    On Tuesday, April 15, 2014 11:47:12 AM UTC-5, skr...@gmail.com wrote:

    I am upgrading from CM 4.8 to CM5.0. HDFS, HBase, Hive, M/R, Impala 1.2.4
    as the major components I use. After upgrading CM 5.0 and following Upgrade
    Cluster path from CM, I am stuck with the below which happens during the
    start phase (after parcel activation).


    Deploy Client Configuration

    Command failed to run because service impala1 has invalid configuration.
    Review and correct its configuration. First error: This version of CM only
    supports Impala 1.2 or above. Upgrade to Impala 1.2+ or CDH 5.


    Is the approach to upgrade to Impala 1.3 through CM 5.0 (the approach I
    have taken) correct?


    Any help is much appreciated.
    To unsubscribe from this group and stop receiving emails from it, send an email to scm-users+unsubscribe@cloudera.org.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedApr 15, '14 at 4:47p
activeApr 16, '14 at 3:39p
posts6
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Skr989: 4 posts Darren Lo: 2 posts

People

Translate

site design / logo © 2022 Grokbase