3

Cloudera Quickstart VM の理解に問題があります。これまでの私の手順の概要を説明してみましょう。

  1. Web サービスに接続してデータ フィードを取り込むために、Kafka を使用して何かを記述したいと考えています。
  2. Cloudera 5.5 クイックスタート VM をプレイグラウンドとして使用します。
  3. Kafka を取得するには、区画から CDH をインストールする必要があります。https://community.cloudera.com/t5/Apache-Hadoop-Concepts-and/cloudera-manager-5-4-0-installing-kafka-parcel-fails/td-p/30615経由
  4. Cloudera VM のデスクトップに気の利いた「Migrate to 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 に答える