I misread my own screenshot, it says 30 minutes, not seconds. Also, I did a restart of NiFi and opened it up in a fresh instance of Chrome; no change. I kicked off a GenerateFlowFile processor and the milliseconds are going up, but the 30 minutes is remaining the same...
-----Original Message----- From: Joseph Niemiec [mailto:[email protected]] Sent: Friday, March 31, 2017 10:41 PM To: [email protected] Subject: Re: NiFi Processors show 30 Second Execution time, 0 executions Doing a clean build of 091359b450a7d0fb6bb04e2238c9171728cd2720, I will have to see if I have a windows 7 VM anywhere, I know Witt was using Win10 and didnt see it... I find it odd that ALL your processors have a 30 second number not just the UpdateAttribute. Anything else about your environment you can share that may be unique? On Fri, Mar 31, 2017 at 10:15 AM, Peter Wicks (pwicks) <[email protected]> wrote: > 091359b450a7d0fb6bb04e2238c9171728cd2720, so just one commit behind > master. > I am testing on Windows 7. > > Lee, yield isn't a bad idea, but UpdateAttribute in my screenshot has > never run; not even once. I don't think it's had the opportunity to yield. > > -----Original Message----- > From: Joseph Niemiec [mailto:[email protected]] > Sent: Friday, March 31, 2017 9:37 PM > To: [email protected] > Subject: Re: NiFi Processors show 30 Second Execution time, 0 > executions > > I just built the latest and am unable to see the issue as well. I also > played with yield duration with no luck. > > Can you provide us what build your on so I can check that one out exactly? > I did my last trunk test as of - > 6a64b3cd9cca70e6a27b9034eba520ae0c0cb6ca > > git rev-parse HEAD > > > On Fri, Mar 31, 2017 at 9:21 AM, Lee Laim <[email protected]> wrote: > > > Is it potentially related to yield duration? > > > > > > > > > On Mar 31, 2017, at 6:58 AM, Peter Wicks (pwicks) > > > <[email protected]> > > wrote: > > > > > > channel. > > > > > > -- > Joseph > -- Joseph
