@Geoffrey Shelton Okot After i set $KAFKA_KERBEROS_PARAMS in my kafka-env.sh file then source kafka-env from kafka-server-start.sh, my problem solved, it seems the param KAFKA_KERBEROS_PARAMS is set to be used by controller. Thanks Geoffrey Shelton Okot. ... View more

@Micaël Dias The same problem occurred to me, it can create topic sucessfully but failed to produce: [root@server30 kafka]# bin/kafka-topics.sh --create --zookeeper server30:2181 --topic S1_MME --replication-factor 1 --partition 2 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. Created topic "S1_MME". [root@server30 kafka]# bin/kafka-console-producer.sh --broker-list server30:9096 --topic S1_MME --producer.config config/producer.properties adsa wqdada xasa [2017-08-26 01:38:43,346] ERROR Error when sending message to topic S1_MME with key: null, value: 4 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) Then I follow your steps, relace old keytab by new one which create with arcfour-hmac encryption, and it changes nothing. The zk authed kafka broker successful: 2017-08-26 01:34:07,215 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:SaslServerCallbackHandler@118] - Successfully authenticated client: authenticationID=kafka/server30@KRBKDC; authorizationID=kafka/server30@KRBKDC. 2017-08-26 01:34:07,215 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:SaslServerCallbackHandler@134] - Setting authorizedID: kafka 2017-08-26 01:34:07,215 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@964] - adding SASL authorization for authorizationID: kafka But the kafka controller still can't connect broker: [2017-08-26 01:51:32,962] WARN [Controller-0-to-broker-0-send-thread], Controller 0's connection to broker localhost:9096 (id: 0 rack: null) was unsuccessful (kafka.controller.RequestSendThread) java.io.IOException: Connection to localhost:9096 (id: 0 rack: null) failed at kafka.utils.NetworkClientBlockingOps$.awaitReady$1(NetworkClientBlockingOps.scala:83) at kafka.utils.NetworkClientBlockingOps$.blockingReady$extension(NetworkClientBlockingOps.scala:93) at kafka.controller.RequestSendThread.brokerReady(ControllerChannelManager.scala:230) at kafka.controller.RequestSendThread.liftedTree1$1(ControllerChannelManager.scala:182) at kafka.controller.RequestSendThread.doWork(ControllerChannelManager.scala:181) at kafka.utils.ShutdownableThread.run(ShutdownableThread.scala:63) Do you have any new find about the issue? I run my zk and kafka on one host, single broker, centos 7 ... View more