Re: PutS3 object returns jvm out of memory

2016-09-20 Thread Aldrin Piri
Hi Selvam, As mentioned, please keep messages to the one list. Moving dev to bcc again. Archiving is only applicable for that content which has exited the flow and is not referenced by any FlowFiles currently in your processing graph, similar to garbage collection in Java. For this particular

Re: PutS3 object returns jvm out of memory

2016-09-20 Thread Selvam Raman
In my case it is going out of disk space. i set nifi.content.repository.archive.enabled=false. (when i changed this have restarted nifi cluster ) But still i can see the processor keep on writing here on the disk. On Tue, Sep 20, 2016 at 4:34 PM, Joe Witt wrote: > Hello >

Re: PutS3 object returns jvm out of memory

2016-09-20 Thread Selvam Raman
This is the exact error. On Tue, Sep 20, 2016 at 4:30 PM, Selvam Raman wrote: > HI, > > I am pushing data to s3 using puts3object. I have setup nifi 1.0 zero > master cluster. > > Ec2 instance having only 8GB of hard disk. Content repository writing till > 4.6 gb of data

PutS3 object returns jvm out of memory

2016-09-20 Thread Selvam Raman
HI, I am pushing data to s3 using puts3object. I have setup nifi 1.0 zero master cluster. Ec2 instance having only 8GB of hard disk. Content repository writing till 4.6 gb of data then it throws jvm out of memory error. I changed nifi.properties for nifi.content.archive to false. but still it

Re: [ANNOUNCE] New Apache NiFi Committer Rob Moran

2016-09-20 Thread Andre
Congratulations Rob and thank you for the work around the new UI. It is awesome. Cheers On Tue, Sep 20, 2016 at 5:08 AM, Tony Kurc wrote: > On behalf of the Apache NiFI PMC, I am very pleased to announce that Rob > Moran has accepted the PMC's invitation to become a

Re: [ANNOUNCE] New Apache NiFi Committer Rob Moran

2016-09-20 Thread Oleg Zhurakousky
Indeed, UI looks pretty awesome now and we all know who’s behind it. Congrats! > On Sep 19, 2016, at 6:05 PM, Joe Witt wrote: > > Pretty cool to see Rob obtain committer status. His efforts arent always > obviously tied to a commit but so much of what people see are his