Minion: Kafka related WARN log messages (AdminClientConfig The configuration X isn't a known config)
Description
Acceptance / Success Criteria
Attachments
related to
Lucidchart Diagrams
Activity

Chantal Moffatt May 19, 2021 at 1:58 PM
HZN 27.2.0 minion still seeing warning logs generated.
05/19/2021 13:55:50 [Warn] org.apache.kafka.clients.admin.AdminClientConfig The configuration 'felix.fileinstall.filename' was supplied but isn't a known config.
05/19/2021 13:55:50 [Warn] org.apache.kafka.clients.admin.AdminClientConfig The configuration 'single-topic' was supplied but isn't a known config.
05/19/2021 13:55:50 [Warn] org.apache.kafka.clients.admin.AdminClientConfig The configuration 'service.pid' was supplied but isn't a known config.

Benjamin Reed March 24, 2021 at 5:23 PM
Merged to foundation-2020

Benjamin Reed March 24, 2021 at 3:16 PM

Benjamin Reed March 24, 2021 at 3:01 PMEdited
It appears that this will be fixed in a future version of Kafka (it will no longer pass through "unrelated" configs when parsing this): https://issues.apache.org/jira/browse/KAFKA-10090
In the meantime, we should be able to turn those to ERROR
or something, and make a note to change it back when we upgrade to 2.8 or higher.
Details
Details
Assignee

Reporter

Labels
Components
Sprint
Fix versions
Priority
PagerDuty
PagerDuty Incident
PagerDuty

SCENARIO:
Minions setup to use Kafka are generating multiple warning logs every 5 seconds during health-check.
The felix.fileinstall.filename and service.pid logs are generated with a vanilla configuration. Additional kafka rpc and ipc settings defined in minion-config.yaml also trigger this warning log (ex: single-topic).
Seen with minion 27.0+.
Hopefully just log noise that still should be either fixed, downgraded from WARN or silenced.
Even if just log noise, we should either fix, downgrade or silence