Peter - that definitely seems odd and thanks for flagging that. I'm not seeing that behavior myself (or at least have not noticed it).
On Fri, Mar 31, 2017 at 8:58 AM, Peter Wicks (pwicks) <[email protected]> wrote: > Not sure why the image didn't come through. I uploaded it to Google Photos, > we'll try that: https://goo.gl/photos/iu1cccMXUf8ntSZV9 > > > -----Original Message----- > From: Joseph Niemiec [mailto:[email protected]] > Sent: Friday, March 31, 2017 8:37 PM > To: [email protected] > Subject: Re: NiFi Processors show 30 Second Execution time, 0 executions > > Are you attempting to also attach a screenshot? My Email seems to think so > but no photo is coming out. The zero tasks makes sense (see below) but I am > not 100% sure where your getting 30 seconds from, maybe another dev has an > idea on that one... Can we get a screenshot? > > ~~ > Ran on 1.1.1... > > Zero tasks makes sense as there has been no work scheduled for the processor. > Otherwise there is no need to run something like the UpdateAttribute > Processor nonstop each time. I went and turned the processor logger to INFO > from WARN (bottom of email) and you see the Timer-Driven Process thread only > log once a flowfile has landed into the channel. Otherwise for 5 minutes > after zipo if no new FlowFiles landed in the channel. > > If we look at the dev docs it mentions mostly the onTrigger and what 'work > scheduled means' (when processors are triggered) > https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#when-processors-are-triggered > > > Quote from the docs > "A Processor’s onTrigger method will be called only when it is scheduled to > run and when work exists for the Processor. Work is said to exist for a > Processor if any of the following conditions is met: > *A Connection whose destination is the Processor has at least one FlowFile in > its queue *The Processors has no incoming Connections *The Processor is > annotated with the @TriggerWhenEmpty annotation" > > > If you keep going they talk about annotations, you could use the onScheduled > annotation if you always wanted to execute the task in a custom processor. > > #INFI UpdateAttribute Processor Logs > 2017-03-31 08:21:22,393 INFO [StandardProcessScheduler Thread-3] > o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled > UpdateAttribute[id=24478d36-015b-1000-ce38-ca50c24234fd] to run with 1 threads > 2017-03-31 08:21:22,570 INFO [Flow Service Tasks Thread-2] > o.a.nifi.controller.StandardFlowService Saved flow controller > org.apache.nifi.controller.FlowController@706b2b31 // Another save pending = > false > 2017-03-31 08:21:34,666 INFO [StandardProcessScheduler Thread-6] > o.a.n.c.s.TimerDrivenSchedulingAgent Scheduled > GenerateFlowFile[id=244774ca-015b-1000-5a1f-9cd57db06ec3] to run with 1 > threads > 2017-03-31 08:21:34,712 INFO [Timer-Driven Process Thread-5] > o.a.n.p.attributes.UpdateAttribute > UpdateAttribute[id=24478d36-015b-1000-ce38-ca50c24234fd] Updated attributes > for > StandardFlowFileRecord[uuid=74742b13-a650-4e19-a2e4-5a8adbfc259d,claim=,offset=0,name=82058058092238,size=0]; > transferring to 'success' > 2017-03-31 08:21:35,077 INFO [Flow Service Tasks Thread-2] > o.a.nifi.controller.StandardFlowService Saved flow controller > org.apache.nifi.controller.FlowController@706b2b31 // Another save pending = > false > 2017-03-31 08:21:36,865 INFO [Provenance Maintenance Thread-2] > o.a.n.p.PersistentProvenanceRepository Created new Provenance Event Writers > for events starting with ID 8 > 2017-03-31 08:21:36,898 INFO [Provenance Repository Rollover Thread-1] > o.a.n.p.PersistentProvenanceRepository Successfully merged 16 journal files > (2 records) into single Provenance Log File ./provenance_repository/6.prov in > 34 milliseconds > 2017-03-31 08:21:36,899 INFO [Provenance Repository Rollover Thread-1] > o.a.n.p.PersistentProvenanceRepository Successfully Rolled over Provenance > Event file containing 2 records. In the past 5 minutes, 2 events have been > written to the Provenance Repository, totaling 638 bytes > 2017-03-31 08:21:37,960 INFO [NiFi Web Server-22] > o.a.n.controller.StandardProcessorNode Stopping processor: class > org.apache.nifi.processors.standard.GenerateFlowFile > 2017-03-31 08:21:37,960 INFO [StandardProcessScheduler Thread-1] > o.a.n.c.s.TimerDrivenSchedulingAgent Stopped scheduling > GenerateFlowFile[id=244774ca-015b-1000-5a1f-9cd57db06ec3] to run > 2017-03-31 08:21:38,081 INFO [Flow Service Tasks Thread-2] > o.a.nifi.controller.StandardFlowService Saved flow controller > org.apache.nifi.controller.FlowController@706b2b31 // Another save pending = > false > 2017-03-31 08:21:46,956 INFO [Write-Ahead Local State Provider Maintenance] > org.wali.MinimalLockingWriteAheadLog > org.wali.MinimalLockingWriteAheadLog@7bebad0d checkpointed with 0 Records and > 0 Swap Files in 15 milliseconds (Stop-the-world time = 0 milliseconds, Clear > Edit Logs time = 0 millis), max Transaction ID -1 > 2017-03-31 08:21:47,253 INFO [pool-8-thread-1] > o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of FlowFile > Repository > 2017-03-31 08:21:47,303 INFO [pool-8-thread-1] > org.wali.MinimalLockingWriteAheadLog > org.wali.MinimalLockingWriteAheadLog@1dce481b checkpointed with 4 Records and > 0 Swap Files in 50 milliseconds (Stop-the-world time = 18 milliseconds, Clear > Edit Logs time = 12 millis), max Transaction ID 7 > 2017-03-31 08:21:47,304 INFO [pool-8-thread-1] > o.a.n.c.r.WriteAheadFlowFileRepository Successfully checkpointed FlowFile > Repository with 4 records in 50 milliseconds > > > On Fri, Mar 31, 2017 at 4:25 AM, Peter Wicks (pwicks) <[email protected]> > wrote: > >> I just noticed that on the latest version (which is now working for >> me) that all processors that have not recently run show 0 Tasks and 30 >> Seconds of Time. Is this a bug, or something that just isn’t obvious? >> >> I previously executed ExecuteSQL and GenerateTableFetch in this view, >> but it was over five minutes ago. UpdateAttribute has never been run. >> >> >> >> >> >> > > > -- > Joseph
