About dlyle

clement_faraon · ‎06-02-2017

solved by using docker method

308741831 · ‎12-10-2016

thanks for your advice!

dlyle · ‎09-14-2016

It had over 10GB free. The webhdfs copy causes the namenode to exhaust its 1GB heap. This is a new behavior with HDP 2.4.3. 2.3.x, 2.4.0, 2.4.2 and 2.5.0 all work in this configuration with the same machines. You may notice from the stack trace, this is prior to the history server trying to actually start.

dlyle · ‎07-27-2016

You're right, I did. Must have had zookeeper stuck in my head. Thanks! Can you start it using Monit?

kpaul · ‎01-20-2017

Hi Ryan, came across this post as I ran into similar issue as above installing metron and tried your steps to resolve. Im now also stuck with a blank Kibana screen but can't or don't seem to have a file "/etc/elasticsearch/elasticsearch.yml" to add the 2 parameters you're suggesting. From the installation steps i can see elasticsearch has been installed and started correctly. Any idea how to resolve, what i could be missing? thx

Online	Offline
Last Visited	‎08-09-2017 07:25 PM

Date Registered	‎09-29-2015 12:15 AM
Last Visited	‎08-09-2017 07:25 PM
Total Messages Posted	44
Total Kudos Received	20

Re: Issue when installing apache metron on sandbox...

Re: Exception in indexingBolt of indexing topology

Re: Apache Metron Single Node Installation Issue: ...

Re: How to install metron without vagrant and on r...

Re: Error in metron dashboard deployment

Re: Issue when installing apache metron on sandbox...

Re: Apache Metron Start the ambari cluster failed

Re: History Server won't start with 1GB Namenode h...

Re: enrichment topology not listing in storm ui

Re: metron singlenode vagrant installation ERROR