Ahhh large merges. Are those still on-going? The solution to that is basically a two phase merge. Merge1 combines up to say 5000 things. Merge2 combines up to 200 things. Now you can merge without ever having more than 5000 flow files attributes in memory. This is a known issue in that people should not have to know this level of detail. We don't have a quick fix in mind for it and the workaround does work quite well.
With this in play can you go ahead and run that command I gave you. If you don't add the last number (the 20) then it will run until you kill it with cntl-c or equivalent. With this we can see if the heap is filling up or GC issues coming into play. Thanks Joe On Sat, Jun 25, 2016 at 3:52 PM, ddewaele <ddewa...@gmail.com> wrote: > Thanks a lot ... I was actually already at 6gb heap. > > > I guess the large number of merges (1.000.000) were causing the original > issue. > > The hangs in the UI I think are unrelated. Again, I'm on 1.0.0-SNAPSHOT. I > have a very simple flow right now that reads an S3 bucket and writes it to a > file. Bucket contains 6 files (50kb each). > > Don't know exactly how to reproduce it, but this usually does it : > > - Stop a processor that's active > - Delete it (pressing backspace quickly - Nifi stays the processor is still > running - probably still shutting down) > - Delete it (again pressing backspace quickly - UI / Nifi process hangs) > > When it hangs it hangs good... I can't do thread dumps on the java process > anymore, and cannot attach with jstat. > > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/UI-can-take-a-very-long-time-to-become-available-tp12201p12265.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
