Katrina, During one execution of the CDC processor, it will handle all available CDC events. State is updated according to the setting of the State Update Interval value. By default it is set to 0, which means state will only be updated when an execution of the processor is completed (or the processor is stopped). If CDC events are streaming in quickly or there are a lot of them queued up, it could take a while before state is updated for the NiFi instance/cluster. You could set State Update Interval to something like 100 msec or whatever, and it will update the state periodically while still processing incoming CDC events.
Regards, Matt On Mon, Jul 23, 2018 at 12:36 PM henriek <[email protected]> wrote: > > Matt, > > I knew I must have been missing something - the setting was set to true. > You're my hero! <fangirling> Thank you! > > (PS - it is working, but does it normally take a while for the viewable > state of the processor to update after it's been cleared? I've cleared state > a couple of times in the past and noticed that it will be blank for a while > before finally showing state...) > > Best, > Katrina > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
