Hi,

I installed Metron 0.7.1 in CentOS 7 with three nodes in EC2 .  Metron
services failing to start. I am getting the below error . As I am setting
up in cloud public IP keeps changing . Where can i config the public IP for
Elastic search server whenever i restart the instances. Is there any good
documentation on the required configuration? Also i was able to install in
single node M4.2x large (32gb) but metron rest fails to start.Kindly
suggest whats the required hardware.

Error

Traceback (most recent call last):
  File 
"/var/lib/ambari-agent/cache/common-services/METRON/0.7.1/package/scripts/rest_master.py",
line 97, in <module>
    RestMaster().execute()
  File 
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 375, in execute
    method(env)
  File 
"/var/lib/ambari-agent/cache/common-services/METRON/0.7.1/package/scripts/rest_master.py",
line 69, in start
    self.configure(env)
  File 
"/usr/lib/ambari-agent/lib/resource_management/libraries/script/script.py",
line 120, in locking_configure
    original_configure(obj, *args, **kw)
  File 
"/var/lib/ambari-agent/cache/common-services/METRON/0.7.1/package/scripts/rest_master.py",
line 47, in configure
    metron_service.refresh_configs(params)
  File 
"/var/lib/ambari-agent/cache/common-services/METRON/0.7.1/package/scripts/metron_service.py",
line 210, in refresh_configs
    check_indexer_parameters()
  File 
"/var/lib/ambari-agent/cache/common-services/METRON/0.7.1/package/scripts/metron_service.py",
line 591, in check_indexer_parameters
    raise Fail("Missing required indexing parameters(s): indexer={0},
missing={1}".format(indexer, missing))
resource_management.core.exceptions.Fail: Missing required indexing
parameters(s): indexer=Elasticsearch, missing=['metron-env/es_hosts']

Node 1 Components
---------------------------


   - Accumulo GC
   - Accumulo Master
   - Accumulo Monitor
   - Accumulo Tracer
   - Activity Analyzer
   - Activity Explorer
   - Atlas Metadata Server
   - DataNode
   - Druid Broker
   - Druid Coordinator
   - Druid Overlord
   - Druid Router
   - Elasticsearch Data Node
   - HBase Client
   - HDFS Client
   - HST Agent
   - HST Server
   - Infra Solr Client
   - Infra Solr Instance
   - Knox Gateway
   - Log Feeder
   - Log Search Server
   - MapReduce2 Client
   - Metrics Monitor
   - Metron Alerts UI
   - Metron Management UI
   - NameNode
   - Spark2 History Server
   - Tez Client
   - YARN Client
   - Zeppelin Notebook
   - ZooKeeper Server


Node 2 components


   - App Timeline Server
   - DataNode
   - DRPC Server
   - HDFS Client
   - History Server
   - Hive Client
   - Hive Metastore
   - HiveServer2
   - HST Agent
   - Log Feeder
   - MapReduce2 Client
   - Metrics Monitor
   - MySQL Server
   - Nimbus
   - Oozie Server
   - Pig Client
   - ResourceManager
   - SNameNode
   - Slider Client
   - Tez Client
   - WebHCat Server
   - YARN Client
   - ZooKeeper Client
   - ZooKeeper Server

Node 3 Components


   - Accumulo Client
   - Accumulo TServer
   - Atlas Metadata Client
   - DataNode
   - Druid Historical
   - Druid MiddleManager
   - Elasticsearch Master
   - Elasticsearch Data Node
   - Flume
   - HBase Client
   - HBase Master
   - RegionServer
   - HCat Client
   - HDFS Client
   - Hive Client
   - HST Agent
   - Infra Solr Client
   - Kafka Broker
   - Kibana Server
   - Log Feeder
   - Mahout Client
   - MapReduce2 Client
   - Metrics Collector
   - Grafana
   - Metrics Monitor
   - Metron Client
   - Metron Enrichment
   - Metron Indexing
   - Metron Parsers
   - Metron PCAP
   - Metron Profiler
   - Metron REST
   - NodeManager
   - Oozie Client
   - Pig Client
   - Slider Client
   - Spark2 Client
   - Sqoop Client
   - Storm UI Server
   - Supervisor
   - Tez Client
   - YARN Client
   - ZooKeeper Client
   - ZooKeeper Server

Thanks and Regards
Hema

Reply via email to