Table of Contents |
---|
Status
Current state: AcceptedAdopted (in 2.2)
Discussion thread: here
JIRA: KAFKA-7352
...
Metrics documenting re-authentications will be maintained in the Selector
code. SOme will mirror existing metrics that document authentications. For example: failed-reauthentication-{rate,total}
and successful-reauthentication-{rate,total}
. There will also be separate successful-authentication-no-reauth-{rate,total}
metrics to indicate the subset of clients that successfully authenticate with a V0 SaslAuthenticateRequest
(or no such request, which can happen with very old clients) These metrics are helpful during migration (see Migration Plan for details) as they will identify if/when all clients are properly upgraded before server-side expired-connection-kill functionality is enabled: the rate metric will be zero across all brokers when it is appropriate to enable the feature, and the total metric will be unchanging (zero after a restart). There will also be reauthentication-latency-{avg,max}
metrics that document the latency imposed by re-authentication. It is unclear if this latency will be problematic, and the data collected via these metrics may be useful as we consider this issue in the future.
...