Hello, I have an issue using using SASL with GSSAPI and kerberos. When I lose a node and a new one is built by our automation all of the kafka nodes continue trying to connect to the replacement node with the old nodes kerberos details which fails. I was expecting KIP-368: "Allow SASL Connections to Periodically Re-Authenticate" to resolve this issue by allowing nodes to clear out their saved credentials and reconnect with new credentials which would fix the problem. After testing kafka 2.2.0 with connections.max.reauth.ms=300000 set on the nodes I am still having the same problem. It doesn't look like kafka is clearing out saved credentials and fully going through the reconnect process to get new credentials for the node. Does anyone know if I am missing something or if this is still an issue with kafka?
Tyler Monahan
