Thanks @MattWho  for your valuable inputs. This is very helpful for conducting the correct analysis on our end. I will check the possibility of customizing the processors that connect to the database.  ... View more

Thank you @MattWho , for the detailed information. Could you please advise whether customization would be beneficial in our situation? Specifically, I would like to know if we can create a CustomDBConnectionService to establish a database connection in NiFi without any pooling. There is a centralized connection pool managed by PgBouncer in our environment that handles pooling. Can you please clarify the below regarding DB connection customization. Is it possible to create a custom database service without utilizing connection pooling? If yes, what would be the impact on the performance of Apache NiFi when local pooling is not enabled? However, I would like to ascertain whether the settings below would effectively lead to the soft or virtual disabling of connection pooling.   Property Name Value Comments Max Idle Connections 0 Set to zero to make sure no idle connections in the pool Minimum Idle Connections 0 Set to zero to make sure no idle connections in the pool Minimum Evictable Idle Time 1 secs Any idle connection will be eligible for eviction after 1 second Soft Minimum Evictable Idle Time 1 secs Any idle connection will be eligible for eviction after 1 second Time Between Eviction Runs 1 secs To run evictor thread every second Max Connection Lifetime -1 Can you clarify what does -1 indicate?  Does it mean no limit on the lifetime of a connection? Max Total Connections -1 Set to negative value to allow unlimited active connections Max Wait Time -1 Set to negative value to allow waiting indefinitely for connections Validation query Null No validation of connection Thanking you for your help!   ... View more

Thank you @MattWho  for providing the details! I now have a much clearer understanding of what was happening. I don't have detailed logs for the last occurrence, but I'll share them if we encounter the issue again. One thing is certain: the node was disconnected due to a discrepancy in the flow.json file. This happened during the deployment of NiFi flows, specifically while upgrading the version of an existing flow. If it had been a standalone execution of the disconnected node, there wouldn't have been an issue, I believe. The actual problem arose because some flow files were stuck in one of the flows, at a connection where load balancing is enabled with the "partition by attribute" strategy (as shown in the image). I assume those records were waiting to be transferred to the other two nodes, which were not accessible to the disconnected node. Could you explain this situation further for my better understanding? That will help us take the right steps. Please let me know if more details are required.       ... View more

Thanks @Shelton for details!!  I will try Option 3 in our pipeline shell script.   Will let you know if any further issues. ... View more

Thank you @MattWho for details. As you mentioned, I will post my usecase in the jira.  Thanks for your help! ... View more

Hi @MattWho      Thanks for info about PutDatabaseRecord cache. We would like to keep PutDatabaseRecord Table schema cache to reduce DB hits.  Is there any option in Nifi to force refresh this Table Schema cache?    ... View more