Our java application connects to confluent cloud kafka - azure to create kafka topics, etc. There are two logs that flows continuosly in our java app, although connection to cluster and creation of topics are successful.
{“message”:“[AdminClient clientId=adminclient-1] Connection to node -1 (pqc-abcny.eastus.azure.confluent.cloud/x.x.x.x:9092) could not be established. Broker may not be available.”,“timestamp”:“2021-11-22T06:38:53.794270Z”,“fields”:{“processId”:“6785@HONC02G93RUMD6M”,“level”:“WARNING”}}
{“message”:“[AdminClient clientId=adminclient-1] Metadata update failed”,“timestamp”:“2021-11-22T06:39:23.806013Z”,“fields”:{“processId”:“6785@HONC02G93RUMD6M”,“level”:“INFO”,“exception”:{“cause”:“Call(callName=fetchMetadata, deadlineMs=1637563163795, tries=1, nextAllowedTryMs=1637563163901) timed out at 1637563163801 after 1 attempt(s)”,“stackTrace”:“org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1637563163795, tries=1, nextAllowedTryMs=1637563163901) timed out at 1637563163801 after 1 attempt(s)\nCaused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting to send the call. Call: fetchMetadata\n”}}}
in general it might be related to the advertised listener parameter in server.properties.
As you are using confluent cloud it should be already configured correctly I guess.
I checked with the latest confluent cli. I was not able to find the advertised listener parameter. Below are the available properties. Is there any other way to debug this issue.
| Id
| Name
| Type
| Ingress
| Egress
| Storage
| Provider
| Availability
| Region
| Status
| Endpoint
| RestEndpoint