FAQ
I've recently upgraded to CM 4.1 FE.

I see impala, and install the service. I've made the necessary config
changes and everything across the board looks "green" and ready to go.

However, when I attempt to start Impala, all services fail to start with
the message: "Command aborted because of exception: Command timed-out after
150 seconds"

When I try to access the Role log files I get a message saying they do not
exist. Any thoughts where I can dig to find out what is failing?

When I run host inspector I get the following:

ImpalaUnavailableNot installed or path incorrectHDFS (CDH4 only)2.0.0+541
CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase
0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper
3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS
(CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NG
UnavailableNot installed or path incorrectCloudera Manager Management
Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

I do not have hbase setup as a service and have set impala hbase usage to
"none".

Thanks,
Jesse

Search Discussions

  • Jesse Edwards at Oct 27, 2012 at 12:03 am
    Thanks so much for your help!

    We're up and running now yay!
  • Jonathan Natkins at Oct 27, 2012 at 12:25 am
    Hi Jesse,

    Out of curiosity, what operating system are you running on?

    Thanks,
    Natty
    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards wrote:

    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start with
    the message: "Command aborted because of exception: Command timed-out
    after 150 seconds"

    When I try to access the Role log files I get a message saying they do not
    exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage to
    "none".

    Thanks,
    Jesse
  • Vinithra Varadharajan at Oct 27, 2012 at 3:20 am
    Jesse,

    Which OS are you using? Impala is currently supported on RHEL6 and CentOS6
    only.

    -Vinithra
    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards wrote:

    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start with
    the message: "Command aborted because of exception: Command timed-out
    after 150 seconds"

    When I try to access the Role log files I get a message saying they do not
    exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage to
    "none".

    Thanks,
    Jesse
  • Jesse Edwards at Oct 27, 2012 at 12:33 am
    Centos 6.3
    On Friday, October 26, 2012 4:29:32 PM UTC-7, Vinithra wrote:

    Jesse,

    Which OS are you using? Impala is currently supported on RHEL6 and CentOS6
    only.

    -Vinithra

    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards <jle.e...@gmail.com<javascript:>
    wrote:
    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start with
    the message: "Command aborted because of exception: Command timed-out
    after 150 seconds"

    When I try to access the Role log files I get a message saying they do
    not exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage to
    "none".

    Thanks,
    Jesse
  • Vikas Singh at Oct 27, 2012 at 12:46 am
    Hi Jesse,

    If you upgrade CM which was managing an existing cluster, then you need to
    install Impala binaries on all nodes of cluster yourself. CM will not do
    that for you. Instructions to install Impala binaries can be found here:
    https://ccp.cloudera.com/display/IMPALA10BETADOC/Installing+Impala

    Once you have installed the binaries and setup Hive metastore correctly,
    you can use CM to manage it.

    - Vikas
    On Fri, Oct 26, 2012 at 4:35 PM, Jesse Edwards wrote:

    Centos 6.3

    On Friday, October 26, 2012 4:29:32 PM UTC-7, Vinithra wrote:

    Jesse,

    Which OS are you using? Impala is currently supported on RHEL6 and
    CentOS6 only.

    -Vinithra

    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards wrote:

    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start with
    the message: "Command aborted because of exception: Command timed-out
    after 150 seconds"

    When I try to access the Role log files I get a message saying they do
    not exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage
    to "none".

    Thanks,
    Jesse
  • Jesse Edwards at Oct 27, 2012 at 12:52 am
    Thanks, I'll give this a try. Will installing these packages create the
    impala user / group or will i need to manually do this as well?

    Jesse
    On Friday, October 26, 2012 4:41:56 PM UTC-7, Vikas Singh wrote:

    Hi Jesse,

    If you upgrade CM which was managing an existing cluster, then you need to
    install Impala binaries on all nodes of cluster yourself. CM will not do
    that for you. Instructions to install Impala binaries can be found here:
    https://ccp.cloudera.com/display/IMPALA10BETADOC/Installing+Impala

    Once you have installed the binaries and setup Hive metastore correctly,
    you can use CM to manage it.

    - Vikas

    On Fri, Oct 26, 2012 at 4:35 PM, Jesse Edwards <jle.e...@gmail.com<javascript:>
    wrote:
    Centos 6.3

    On Friday, October 26, 2012 4:29:32 PM UTC-7, Vinithra wrote:

    Jesse,

    Which OS are you using? Impala is currently supported on RHEL6 and
    CentOS6 only.

    -Vinithra

    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards wrote:

    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start
    with the message: "Command aborted because of exception: Command
    timed-out after 150 seconds"

    When I try to access the Role log files I get a message saying they do
    not exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage
    to "none".

    Thanks,
    Jesse
  • Vinithra Varadharajan at Oct 27, 2012 at 2:16 am
    Jesse,
    This document might help you in setting up the Hive metastore and
    configuring Impala:
    https://ccp.cloudera.com/display/ENT41DOC/Installing+Impala+with+Cloudera+Manager
    On Fri, Oct 26, 2012 at 4:41 PM, Vikas Singh wrote:

    Hi Jesse,

    If you upgrade CM which was managing an existing cluster, then you need to
    install Impala binaries on all nodes of cluster yourself. CM will not do
    that for you. Instructions to install Impala binaries can be found here:
    https://ccp.cloudera.com/display/IMPALA10BETADOC/Installing+Impala

    Once you have installed the binaries and setup Hive metastore correctly,
    you can use CM to manage it.

    - Vikas

    On Fri, Oct 26, 2012 at 4:35 PM, Jesse Edwards wrote:

    Centos 6.3

    On Friday, October 26, 2012 4:29:32 PM UTC-7, Vinithra wrote:

    Jesse,

    Which OS are you using? Impala is currently supported on RHEL6 and
    CentOS6 only.

    -Vinithra

    On Fri, Oct 26, 2012 at 4:26 PM, Jesse Edwards wrote:

    I've recently upgraded to CM 4.1 FE.

    I see impala, and install the service. I've made the necessary config
    changes and everything across the board looks "green" and ready to go.

    However, when I attempt to start Impala, all services fail to start
    with the message: "Command aborted because of exception: Command
    timed-out after 150 seconds"

    When I try to access the Role log files I get a message saying they do
    not exist. Any thoughts where I can dig to find out what is failing?

    When I run host inspector I get the following:

    Impala Unavailable Not installed or path incorrect HDFS (CDH4 only)2.0.0+541CDH4Hue Plugins2.1.0+208CDH4MapReduce 2 (CDH4 only)2.0.0+541CDH4HBase0.92.1+154CDH4Oozie3.2.0+121CDH4Yarn (CDH4 only)2.0.0+541CDH4Zookeeper3.4.3+25CDH4Hue2.1.0+208CDH4MapReduce 1 (CDH4 only)0.20.2+1259CDH4HttpFS (CDH4 only)2.0.0+541CDH4Hadoop2.0.0+541CDH4Hive0.9.0+148CDH4Flume NGUnavailableNot installed or path incorrectCloudera Manager Management Daemons4.1.0Not applicableCloudera Manager Agent4.1.0Not applicable

    I do not have hbase setup as a service and have set impala hbase usage
    to "none".

    Thanks,
    Jesse

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedOct 27, '12 at 12:03a
activeOct 27, '12 at 3:23a
posts8
users4
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase