I have a problem with Datahub to Amazon MKS. Following the documentation – https://datahubproject.io/docs/deploy/aws I have created a MKS cluster and changes to global- kafka section in values.yaml to the following: kafka: bootstrap: server: “<bootstrap_server_1>9092,&lt;bootstrap server 2&gt;9092” zookeeper: server: “<zookeeper_server_1>:2182, “<zookeeper_server_2>::2182, “<zookeeper_server_3>::2182” ## For AWS MSK set this to a number larger than 1 partitions: 2 replicationFactor: 2 schemaregistry: url: “http://prerequisites-cp-schema-registry:8081” # type: AWS_GLUE # glue: # region: us-east-1 # registry: datahub For <bootstrap_server_1>9092,&lt;bootstrap server 2&gt;9092 I have copied the values from View client information- Bootstrap servers- plaintext, And respectively for “<zookeeper_server_1>:2182, “<zookeeper_server_2>::2182, “<zookeeper_server_3>::2182 From Apache ZooKeeper connection - plaintext However when I run helm upgrade --install datahub datahub/datahub --values values.yaml the upgrade fails and the logs datahub-kafka-setup-job becomes in status Error. Looking at its logs I see the following problem: [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: 1661858565207 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 b-2.datahubcbdevkafka.qdtcf8.c16.kafka.us-east-1.amazonaws.com:9092,b-1.datahubcbdevkafka.qdtcf8.c16.kafka.us-east-1.amazonaws.com: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: Has anyone encountered this before and can help me fix it?

Hi @bumpy-journalist-41369, gentle reminder to please follow our slack guidelines & post large blocks of code/stack trace in threads. it’s a HUGE help for us to keep track of unanswered questions across our various support channels teamwork

You can view our Slack Gluidelines here: https://datahubproject.io/docs/slack/