[jira] [Updated] (NIFI-12194) Nifi fails when ConsumeKafka_2_6 processor is started with PLAINTEXT securityProtocol

["Peter Schmitzer (Jira)" <ji...@apache.org>]

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

Peter Schmitzer updated NIFI-12194:
-----------------------------------
    Affects Version/s: 1.23.0

> Nifi fails when ConsumeKafka_2_6 processor is started with PLAINTEXT securityProtocol
> -------------------------------------------------------------------------------------
>
>                 Key: NIFI-12194
>                 URL: https://issues.apache.org/jira/browse/NIFI-12194
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.21.0, 1.23.0
>            Reporter: Peter Schmitzer
>            Priority: Major
>         Attachments: image-2023-09-27-15-56-02-438.png
>
>
> When starting ConsumeKafka_2_6 processor with sasl mechanism GSSAPI and the securityProtocol PLAINTEXT (although SSL would be correct) the UI crashed and nifi was no longer accessible. Not only the frontend was not accessible anymore, also the other processors in our flow stopped performing well according to our dashboards.
> We were able to reproduce this by using the config as described above.
> Our nifi in preprod (where this was detected) runs in a kubernetes cluster.
>  * version 1.21.0
>  * 3 nodes
>  * jvmMemory: 1536m
>  * 3G memory (limit)
>  * 400m cpu (request)
>  * zookeeper
> The logs do not offer any unusual entries when the issue is triggered. Inspecting the pod metrics we found a spike in memory.
> The issue is a bit scary for us because a rather innocent config parameter in one single processor is able to let our whole cluster break down.
>  



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