3

我在理解 Cloudera Quickstart VM 的某些内容时遇到问题。让我通过概述到目前为止的步骤来尝试解释。

  1. 我想使用 Kafka 编写一些东西来连接到 Web 服务并摄取数据馈送。
  2. 我将使用 Cloudera 5.5 快速入门 VM 作为我的游乐场。
  3. 我需要从包裹中安装 CDH 才能获得 Kafka。通过https://community.cloudera.com/t5/Apache-Hadoop-Concepts-and/cloudera-manager-5-4-0-installing-kafka-parcel-fails/td-p/30615
  4. 我在 Cloudera VM 的桌面上看到了一个漂亮的“迁移到 Parcels”图标,所以我单击它并让它完成。
  5. 我尝试启动 cloudera 服务,现在我得到以下所有这些 -

    impala-server: unrecognized service
    
    impala-catalog: unrecognized service
    sqoop-metastore: unrecognized service
    solr-server: unrecognized service
    oozie: unrecognized service
    impala-state-store: unrecognized service
    hue: unrecognized service
    flume-ng-agent: unrecognized service
    hbase-regionserver: unrecognized service
    sqoop2-server: unrecognized service
    spark-history-server: unrecognized service
    sentry-store: unrecognized service
    hive-server2: unrecognized service
    hive-metastore: unrecognized service
    hbase-thrift: unrecognized service
    hbase-rest: unrecognized service
    hbase-master: unrecognized service
    hadoop-yarn-resourcemanager: unrecognized service
    hadoop-yarn-proxyserver: unrecognized service
    hadoop-yarn-nodemanager: unrecognized service
    hadoop-mapreduce-historyserver: unrecognized service
    hadoop-httpfs: unrecognized service
    hadoop-hdfs-secondarynamenode: unrecognized service
    hadoop-hdfs-namenode: unrecognized service
    hadoop-hdfs-journalnode: unrecognized service
    hadoop-hdfs-datanode: unrecognized service
    hbase-solr-indexer: unrecognized service
    zookeeper-server: unrecognized service
    [QuickStart] Disabling CDH services on boot...
    error reading information on service impala-server: No such file or directory
    error reading information on service impala-catalog: No such file or directory
    error reading information on service sqoop-metastore: No such file or directory
    error reading information on service solr-server: No such file or directory
    error reading information on service oozie: No such file or directory
    error reading information on service impala-state-store: No such file or directory
    error reading information on service hue: No such file or directory
    error reading information on service flume-ng-agent: No such file or directory
    error reading information on service hbase-regionserver: No such file or directory
    error reading information on service sqoop2-server: No such file or directory
    error reading information on service spark-history-server: No such file or directory
    error reading information on service sentry-store: No such file or directory
    error reading information on service hive-server2: No such file or directory
    error reading information on service hive-metastore: No such file or directory
    error reading information on service hbase-thrift: No such file or directory
    error reading information on service hbase-rest: No such file or directory
    error reading information on service hbase-master: No such file or directory
    error reading information on service hadoop-yarn-resourcemanager: No such file or directory
    error reading information on service hadoop-yarn-proxyserver: No such file or directory
    error reading information on service hadoop-yarn-nodemanager: No such file or directory
    error reading information on service hadoop-mapreduce-historyserver: No such file or directory
    error reading information on service hadoop-httpfs: No such file or directory
    error reading information on service hadoop-hdfs-secondarynamenode: No such file or directory
    error reading information on service hadoop-hdfs-namenode: No such file or directory
    error reading information on service hadoop-hdfs-journalnode: No such file or directory
    error reading information on service hadoop-hdfs-datanode: No such file or directory
    error reading information on service hbase-solr-indexer: No such file or directory
    error reading information on service zookeeper-server: No such file or directory
    [QuickStart] Starting Cloudera Manager daemons...
    [QuickStart] Waiting for Cloudera Manager API...
    

后来,当我执行“top”命令时,我显然看不到进程正在运行。我还应该做什么?

4

1 回答 1

2

这是一个超级简单的修复。我启动了cloudera manager服务

service cloudera-scm-server restart

我启动了 cloudera 代理

service cloudera-scm-agent restart

在http://quickstart.cloudera:7180/cmf/home进入 Cloudera Manager Home

然后在状态选项卡中,我刚刚启动了每个服务。这一切都是用 GUI 完成的,很容易

于 2015-12-30T08:27:59.447 回答