Java kafka AdminClient compatibility

[gustavomonarin]

Where could i check / dive the kafka AdminClient compatibility?

I see in the docs some especial port for the admin, but it feels to be different thing, more like a redpanda admin.

I am using Redpanda in development mode, for tests using the standard java kafka library and test containers.

Given:

AdminClient.create(
  new Properties() {{
                put(AdminClientConfig.BOOTSTRAP_SERVERS_CONFIG, bootstrapServers);
  }}
);

i see the following errors:

 main] o.a.k.clients.admin.AdminClientConfig    : AdminClientConfig values: 
	bootstrap.servers = [PLAINTEXT://localhost:52827]
	client.dns.lookup = use_all_dns_ips
	client.id = 
	connections.max.idle.ms = 300000
	default.api.timeout.ms = 60000
	metadata.max.age.ms = 300000
	metric.reporters = []
	metrics.num.samples = 2
	metrics.recording.level = INFO
	metrics.sample.window.ms = 30000
	receive.buffer.bytes = 65536
	reconnect.backoff.max.ms = 1000
	reconnect.backoff.ms = 50
	request.timeout.ms = 30000
	retries = 2147483647
	retry.backoff.ms = 100
	sasl.client.callback.handler.class = null
	sasl.jaas.config = null
	sasl.kerberos.kinit.cmd = /usr/bin/kinit
	sasl.kerberos.min.time.before.relogin = 60000
	sasl.kerberos.service.name = null
	sasl.kerberos.ticket.renew.jitter = 0.05
	sasl.kerberos.ticket.renew.window.factor = 0.8
	sasl.login.callback.handler.class = null
	sasl.login.class = null
	sasl.login.refresh.buffer.seconds = 300
	sasl.login.refresh.min.period.seconds = 60
	sasl.login.refresh.window.factor = 0.8
	sasl.login.refresh.window.jitter = 0.05
	sasl.mechanism = SCRAM-SHA-256
	security.protocol = PLAINTEXT
	security.providers = null
	send.buffer.bytes = 131072
	socket.connection.setup.timeout.max.ms = 127000
	socket.connection.setup.timeout.ms = 10000
	ssl.cipher.suites = null
	ssl.enabled.protocols = [TLSv1.2, TLSv1.3]
	ssl.endpoint.identification.algorithm = 
	ssl.engine.factory.class = null
	ssl.key.password = null
	ssl.keymanager.algorithm = SunX509
	ssl.keystore.certificate.chain = null
	ssl.keystore.key = null
	ssl.keystore.location = null
	ssl.keystore.password = null
	ssl.keystore.type = JKS
	ssl.protocol = SSL
	ssl.provider = null
	ssl.secure.random.implementation = null
	ssl.trustmanager.algorithm = PKIX
	ssl.truststore.certificates = null
	ssl.truststore.location = /deploy/certs/ca.pem
	ssl.truststore.password = null
	ssl.truststore.type = PEM

2022-12-15 19:08:32.980  INFO 20515 --- [           main] o.a.kafka.common.utils.AppInfoParser     : Kafka version: 2.7.2
2022-12-15 19:08:32.980  INFO 20515 --- [ adminclient-22] o.a.kafka.common.utils.AppInfoParser     : App info kafka.admin.client for adminclient-22 unregistered
2022-12-15 19:08:32.980  INFO 20515 --- [ adminclient-22] o.a.k.c.a.i.AdminMetadataManager         : [AdminClient clientId=adminclient-22] Metadata update failed

org.apache.kafka.common.errors.TimeoutException: Call(callName=fetchMetadata, deadlineMs=1671131342980, tries=1, nextAllowedTryMs=-9223372036854775709) timed out at 9223372036854775807 after 1 attempt(s)
Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting to send the call. Call: fetchMetadata

[emaxerrno]

afaik only moving partitions should be missing. everythying else should be good (should be landing soon)

this error is not about the admin api, this error says that your listeners are incorrectly configured a network timeout means the tcp conn is not working.... meaning you haven't gotten to the kafka api layer yet.

[gustavomonarin]

Thank you Alexander for a so fast reply.

Indeed i noticed the timeout message, however i was a bit biased on the java AdminClient as it is the only new part.

Both Kafka Producers and Kafka consumers are able to reach out the same bootstrap.servers in the same test, so it makes me feel it is not a general network issue. I will double check some other AdminClient examples.