@satz , I am not referring to writing data using Kafka connect.   Kafka partition data should be written to cloud after spending certain amount of time on Disk. https://docs.confluent.io/platform/current/kafka/tiered-storage.html Thanks, Uday ... View more

Hi @Babasaheb,   I am expecting to rebalance leaders and replicas. In the example below when broker id 1111 went down, CC self healed(distributed leaders/partitions automatically) to other nodes. When 1111 node came back, distribution not happening automatically.   BROKER LEADER(S) REPLICAS OUT-OF-SYNC OFFLINE IS_CONTROLLER 1234              36             118                 0                     0                     false 5678               44             123                0                     0                     false 1111                 0                0                  0                     0                     false 3333               44             126                0                     0                     false 4444               44             126                0                     0                      true   Thanks, Uday ... View more

Hello Babasaheb,   Self healing is enabled already. When any broker goes down, CC is rebalancing partitions to healthy nodes but when that node comes back up, redistribution is not happening automatically. I have to run the rebalance API manually.   self.healing.broker.failure.enabled=true self.healing.disk.failure.enabled=true broker.failure.alert.threshold.ms=60000 broker.failure.self.healing.threshold.ms=120000   Thanks, Uday ... View more

Hi André,   With or without domain in the configuration, its taking default domain.  If we provide multiple domains also its not authenticating new one.   Thanks, Uday ... View more

Hello André,   I am observing below error after updating LDAP User DN Template to {0}. Fun part is without mentioning any domain, previous domain user is still able to connect but new domain user connectivity fails.   22/09/02 08:20:02 WARN internals.AdminMetadataManager: [AdminClient clientId=adminclient-1] Metadata update failed due to authentication error org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed: Invalid username or password Error while executing topic command : org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed: Invalid username or password 22/09/02 08:20:02 ERROR admin.TopicCommand$: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.SaslAuthenticationException: Authentication failed: Invalid username or password 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:89) at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260) at kafka.admin.TopicCommand$AdminClientTopicService.getTopics(TopicCommand.scala:333) at kafka.admin.TopicCommand$AdminClientTopicService.describeTopic(TopicCommand.scala:288) at kafka.admin.TopicCommand$.main(TopicCommand.scala:68) at kafka.admin.TopicCommand.main(TopicCommand.scala)   Thanks, Uday ... View more

Hi André,   Kerberos is already enabled, we have few users who don't want to use Kerberos which is why we are exploring LDAP.   Thanks, Uday ... View more