@bumpy-needle-3184 Please advise.[main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka version: 6.1.4-ccs [main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka commitId: c9124241a6ff43bc [main] INFO org.apache.kafka.common.utils.AppInfoParser - Kafka startTimeMs: 1662720480602 WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. WARNING: Due to limitations in metric names, topics with a period ('.') or underscore ('_') could collide. To avoid issues it is best to use either, but not both. Error while executing config command with args '--command-config /tmp/connection.properties --bootstrap-server kafka-886515205-1-1200869063.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092,kafka-886515205-2-1200869066.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092,kafka-886515205-3-1200869069.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092,kafka-886515205-4-1200869072.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092,kafka-886515205-5-1200869075.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092,kafka-886515205-6-1200869078.scus.kafka-sams-edf-stg.ms-df-messaging.stg-az-southcentralus-8.prod.us.walmart.net:9092 --entity-type topics --entity-name _schemas --alter --add-config cleanup.policy=compact' java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45) at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32) at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:104) at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:272) at kafka.admin.ConfigCommand$.getResourceConfig(ConfigCommand.scala:552) at kafka.admin.ConfigCommand$.alterConfig(ConfigCommand.scala:322) at kafka.admin.ConfigCommand$.processCommand(ConfigCommand.scala:302) at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:97) at kafka.admin.ConfigCommand.main(ConfigCommand.scala) Caused by: org.apache.kafka.common.errors.UnknownTopicOrPartitionException:

_schemas

topic is created/used by schema-registry . Have you setup schema-registry - https://github.com/acryldata/datahub-helm/blob/master/charts/prerequisites/values.yaml#:~:text=cp%2Dschema%2Dregistry,enabled%3A%20true . If yes ,please try restarting schema-registry pod. Also check if you are able to ping/reach kafka bootstrap server from schma-registry pod.

yes.

also look for any errors in kafka-setup jobs

if there is an error, 0.8.41 version also should failed if am not wrong.

you were getting different errors with older version, may be you didn't reach till this stage to get this error.

we are not using cloudnative elasticsearch, we have install elasticsearch on top of an vm from ami.

okay

Nope, Not yet resolved