That did the trick... I assumed it would be something like that, but assumed it would apply sufficient back-pressure to stop the flow from getting flooded....
With the 10000 x 100 approach things have stabilised, but I'm still seeing frequent hangs in the UI, forcing me to restart Nifi (This usually happens when I edit the flow, stop/start processors, deleting/editing/adding connections). The refresh icon appears in the toolbar and sits there forever. The date/time on the left of it remains stale. - At 1 point it "crashed" when all queues were empty and 90% of the flow was stopped. I was simply modifying the flow (I did a copy - paste of a processor, the refresh icon kicked in and remained there. cpu was spiking as well). There was some logging in the logfiles but the ui / api were not responding. Is this a known issue (perhaps with a JIRA ticket already created )? -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/UI-can-take-a-very-long-time-to-become-available-tp12201p12246.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
