That being said, I would highly suggest experimenting in a cluster; for instance using our automated AWS deployment mechanism [1]. This will spin-up a full cluster (a totally open, unsecured cluster that you need to secure yourself) in AWS.
Of course, this will cost you money, but should you have the funds, this is the way to go. [1] https://github.com/apache/metron/tree/master/metron- deployment/amazon-ec2 On Wed, Jul 19, 2017 at 10:52 AM, Nick Allen <[email protected]> wrote: > Yes, you can try to increase the amount of memory, as long as you have > enough physical memory on your machine. I don't know of any hard memory > limits on that VM. > > On Wed, Jul 19, 2017 at 9:44 AM, Lehuede sebastien <[email protected]> > wrote: > >> Hi Nick, >> >> Yes, i run Nifi directly in "Full Dev VM". I will try to reinstall and >> reconfigure Nifi in an other VM or is it possible to simply increase amount >> of Memory for "Full Dev VM ? >> >> Thanks, >> >> Sebastien. >> >> 2017-07-19 15:13 GMT+02:00 Nick Allen <[email protected]>: >> >>> Are you also running Nifi in your "Full Dev" VM? If so, I would assume >>> that you just don't have enough resources to run all that on one VM. Just >>> running Metron's components alone in "Full Dev" has taken considerable >>> effort to tune. Adding Nifi would probably cause some weird errors due to >>> resource constraints. >>> >>> On Wed, Jul 19, 2017 at 8:50 AM, Lehuede sebastien <[email protected]> >>> wrote: >>> >>>> Hello, >>>> >>>> I have successfully deployed Metron 0.4.0 full dev platform. After >>>> that, i have tried to add a new telemetry data source with this tutorial : >>>> https://cwiki.apache.org/confluence/display/METRON >>>> /Adding+a+New+Telemetry+Data+Source. But when i start NiFi processor, >>>> i don't see any logs in Storm UI and no Elasticsearch index are created. >>>> >>>> I had no error, in NiFi interface when i start processor everything >>>> seem to be OK and in my Ambari interface all services are started, except >>>> "Metron REST". >>>> >>>> I have setting up a very simple grok parser >>>> ("%{DATA:toto}\:%{DATA:tata}") for testing purpose. My goal is to parse a >>>> simple text file who contains things like "bob:alice". >>>> >>>> How can i troubleshoot this problem ? With which logs ? >>>> Has anyone ever had this problem ? >>>> >>>> Thanks, >>>> >>>> Sebastien. >>>> >>>> >>> >> >
