[
https://issues.apache.org/jira/browse/KAFKA-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch updated KAFKA-7248:
---------------------------------
Component/s: (was: KafkaConnect)
core
> Kafka creating topic with no leader. Issue started showing up after
> unkerberizing the cluster
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-7248
> URL: https://issues.apache.org/jira/browse/KAFKA-7248
> Project: Kafka
> Issue Type: Bug
> Components: clients, core
> Affects Versions: 1.0.0
> Environment: Azure Cluster with HDP : 2.6.5 & HDF 3.1
> Reporter: Umesh Bansod
> Priority: Critical
>
> Kafka fails to assign Leader to Topics created by Atlas or manually(from
> command line)
> This started to happen after disabling kerberos from the Cluster.
> I have Tried,
> * Cleaning the ZK
> * Cleaning Kafka metadata
> * Syncing conf with all node clinets
> *Kafka Version*: 1.0.0.2
> *HDP version*: 2.6.5
> *Kafka Cli:*
> --describe --topic ATLAS_HOOK
> Topic:ATLAS_HOOK PartitionCount:1 ReplicationFactor:3 Configs:
> MarkedForDeletion:true
> Topic: ATLAS_HOOK Partition: 0 Leader: *none* Replicas: 1001,1002,1003 Isr:
> */var/log/kafka/server/log:*
> TRACE [Kafka Request Handler 5 on Broker 1002], Kafka request handler 5 on
> broker 1002 handling request Request(processor=0,
> connectionId=10.165.132.8:6667-10.165.132.4:39378-0,
> session=Session(User:ANONYMOUS,/10.165.132.4),
> listenerName=ListenerName(PLAINTEXT), securityProtocol=PLAINTEXT,
> buffer=null) (kafka.server.KafkaRequestHandler)
> [2018-08-05 13:47:51,209] TRACE [KafkaApi-1002] Handling
> request:RequestHeader(apiKey=METADATA, apiVersion=5, clientId=producer-1,
> correlationId=34390) -- \{topics=[ATLAS_HOOK],allow_auto_topic_creation=true}
> from connection
> 10.165.132.8:6667-10.165.132.4:39378-0;securityProtocol:PLAINTEXT,principal:User:ANONYMOUS
> (kafka.server.KafkaApis)
>
> *zookeeper error:*
> INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread@1142] - Unable to
> read additional data from server sessionid 0x36505af3670006a, likely server
> has closed socket, closing socket connection and attempting reconnect
> WATCHER::
> WatchedEvent state:Disconnected type:None path:null
> 2018-08-05 14:33:19,172 - INFO
> [main-SendThread(localhost:2181):ClientCnxn$SendThread@1019] - Opening socket
> connection to server localhost/127.0.0.1:2181. Will not attempt to
> authenticate using SASL (unknown error)
> 2018-08-05 14:33:19,174 - INFO
> [main-SendThread(localhost:2181):ClientCnxn$SendThread@864] - Socket
> connection established, initiating session, client: /127.0.0.1:57774, server:
> localhost/127.0.0.1:2181
> 2018-08-05 14:33:20,027 - INFO
> [main-SendThread(localhost:2181):ClientCnxn$SendThread@1142] - Unable to read
> additional data from server sessionid 0x36505af3670006a, likely server has
> closed socket, closing socket connection and attempting reconnect
> 2018-08-05 14:33:21,457 - INFO
> [main-SendThread(localhost:2181):ClientCnxn$SendThread@1019] - Opening socket
> connection to server localhost/0:0:0:0:0:0:0:1:2181. Will not attempt to
> authenticate using SASL (unknown error)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
