You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:06 UTC
[jira] [Resolved] (NIFI-9257) ExecuteSQLRecord processor doesn't honor the max wait time config when set to 5mins
[ https://issues.apache.org/jira/browse/NIFI-9257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard resolved NIFI-9257.
----------------------------------
Resolution: Feedback Received
Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.
> ExecuteSQLRecord processor doesn't honor the max wait time config when set to 5mins
> -----------------------------------------------------------------------------------
>
> Key: NIFI-9257
> URL: https://issues.apache.org/jira/browse/NIFI-9257
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.12.1
> Environment: software platform
> Reporter: sneha sriram
> Priority: Major
>
> For postgres function/SQL which take longer to run(~more than 5 min),
> Assume SQL takes 8 min to complete, so to avoid query getting killed by ExecuteSQLRecord processor ( with Max Wait time = 5 min), need to increase Max Wait time > 8 min. So updated Max Wait time = 10 mins
> * ExecuteSQLRecord processor receives flow files from incoming queue
> * ExecuteSQLRecord processor triggers/submit postgres functions/SQL to aurora postgres server
> * If aurora postgres function/SQL is taking longer to process(~more than 5 min), *ExecuteSQLRecord processor is getting stuck in running state,* even after postgres function/SQL completes its execution on aurora postgres server
> * It stays in running stuck state indefinitely
> * All downstream processors are not getting any flow files to run
> * This issue was observed with different postgres functions and SQLs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)