Hi Deepanshu, Assuming your flow is a QueryDatabaseTable followed later in the flow by a PutDatabaseRecord, then it is recommended to use CRON-driven scheduling for QueryDatabaseTable and Timer-driven scheduling for PutDatabaeRecord.
If you set both processors to the same CRON schedule, then PutDatabaseRecord will trigger and have nothing to do, because QueryDatabaseTable has triggered at the exact same time but takes a bit of time to complete its job and create a flowfile in NiFi. Regards, -- Mike On Wed, Oct 23, 2024 at 6:50 AM Deepanshu Lodhi <[email protected]> wrote: > Hello Everyone, > > > > *I hope you're doing well!* > > > > I'm encountering a delay with the *PutDatabaseRecord* processor when > inserting data at a scheduled time using CRON-driven scheduling. While the > *QueryDatabaseTable* processor fetches the data on time, the insertion > through *PutDatabaseRecord* is significantly delayed. However, when using > Time-driven scheduling, the processor works as expected without delays. > > I suspect the issue might be related to the *DBCPConnectionPool* > configuration. Could anyone suggest the best possible configuration or > other optimizations to ensure timely data insertion? > > > > Thank you in advance for your support! > > > > Best regards, > Deepanshu > > >
