You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Lou Vasquez (Jira)" <ji...@apache.org> on 2026/03/16 23:59:00 UTC

[jira] [Updated] (NIFI-15535) AWS Controller Service Fault

     [ https://issues.apache.org/jira/browse/NIFI-15535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou Vasquez updated NIFI-15535:
-------------------------------
    Attachment: lv_connection_pool.log
                lv_fix-aws-sts-connection-pool.patch
                lv_simple_connect_pool_bug_flow.json

> AWS Controller Service Fault
> ----------------------------
>
>                 Key: NIFI-15535
>                 URL: https://issues.apache.org/jira/browse/NIFI-15535
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 2.7.2
>         Environment: Test and Prod
>            Reporter: Christopher Gambino
>            Priority: Major
>         Attachments: image-2026-02-02-09-54-53-956.png, jirasamplenifibug.txt, lv_connection_pool.log, lv_fix-aws-sts-connection-pool.patch, lv_simple_connect_pool_bug_flow.json
>
>
> NiFi's AWS connection pool service is failing after the upgrade to 2.7.2  This has been observed across multiple environments that were being upgraded from 2.6.x.  These environments have previously not had any issues with NiFi's connection to AWS.  These happen during times of both high and low load so we do not believe it is load or memory related.  The bug is observed primarily on SQS and s3 processors as that what our flow has, we do not have other processor types to validate against
>  
> The pods are running on EKS with pod level identity set
>  
> For security reasons I cant post the whole log but the main errors are shown in the attached screenshots and text files
>  
> !image-2026-02-02-09-54-53-956.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)