Description
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.
Attachments
Attachments
Issue Links
- is related to
-
KAFKA-4090 JVM runs into OOM if (Java) client uses a SSL port without setting the security protocol
-
- In Progress
-
- links to
