[
https://issues.apache.org/jira/browse/KAFKA-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jorge Machado resolved KAFKA-6017.
----------------------------------
Resolution: Not A Problem
On my side this was a missed configuration on kafka + cdh that broke the
internal topics from kafka. We add the wrong admin users
> Cannot get broker ids from Kafka using kafka-connect
> ----------------------------------------------------
>
> Key: KAFKA-6017
> URL: https://issues.apache.org/jira/browse/KAFKA-6017
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.2.0
> Reporter: Jorge Machado
>
> Hi guys,
> I'm using CDH Kafka 0.10.2.1-cp2 and the confluent 3.2.0 with Kerberos.
> It seems that it cannot get the broker id's and it adds it with -1, -2 etc...
> On Debug mode I see :
> Cluster(id = null, nodes = [host1:9092 (id: -2 rack: null), host2:9092 (id:
> -3 rack: null), host3:9092 (id: -1 rack: null)], partitions = [])
> On Zookeeper I see:
> ls /kafka-prod/brokers/ids
> [264, 265, 263]
> I'm using this command:
> KAFKA_OPTS=-Djava.security.auth.login.config=/etc/kafka/connect_distributed_jaas.conf
> connect-distributed /etc/kafka/connect-distributed.properties
> {code:java}
> [2017-10-06 08:47:52,078] DEBUG Recorded API versions for node -3:
> (Produce(0): 0 to 2 [usable: 2], Fetch(1): 0 to 3 [usable: 3], Offsets(2): 0
> to 1 [usable: 1], Metadata(3): 0 to 2 [usable: 2], LeaderAndIsr(4): 0
> [usable: 0], StopReplica(5): 0 [usable: 0], UpdateMetadata(6): 0 to 3
> [usable: 3], ControlledShutdown(7): 1 [usable: 1], OffsetCommit(8): 0 to 2
> [usable: 2], OffsetFetch(9): 0 to 2 [usable: 2], GroupCoordinator(10): 0
> [usable: 0], JoinGroup(11): 0 to 1 [usable: 1], Heartbeat(12): 0 [usable: 0],
> LeaveGroup(13): 0 [usable: 0], SyncGroup(14): 0 [usable: 0],
> DescribeGroups(15): 0 [usable: 0], ListGroups(16): 0 [usable: 0],
> SaslHandshake(17): 0 [usable: 0], ApiVersions(18): 0 [usable: 0],
> CreateTopics(19): 0 to 1 [usable: 1], DeleteTopics(20): 0 [usable: 0])
> (org.apache.kafka.clients.NetworkClient:558)
> {code}
> At the end I get this error:
> {code}
> [main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started
> o.e.j.s.ServletContextHandler@593e824f{/,null,AVAILABLE}
> [main] INFO org.eclipse.jetty.server.ServerConnector - Started
> ServerConnector@2cab9998{HTTP/1.1}{host:8083}
> [main] INFO org.eclipse.jetty.server.Server - Started @1469ms
> [main] INFO org.apache.kafka.connect.runtime.rest.RestServer - REST server
> listening at http://HOST:8083/, advertising URL http://HOST:8083/
> [main] INFO org.apache.kafka.connect.runtime.Connect - Kafka Connect started
> [DistributedHerder] ERROR
> org.apache.kafka.connect.runtime.distributed.DistributedHerder - Uncaught
> exception in herder work thread, exiting:
> org.apache.kafka.connect.errors.ConnectException: Could not look up partition
> metadata for offset backing store topic in allotted period. This could
> indicate a connectivity issue, unavailable topic partitions, or if this is
> your first use of the topic it may have taken too long to create.
> at
> org.apache.kafka.connect.util.KafkaBasedLog.start(KafkaBasedLog.java:133)
> at
> org.apache.kafka.connect.storage.KafkaOffsetBackingStore.start(KafkaOffsetBackingStore.java:86)
> at org.apache.kafka.connect.runtime.Worker.start(Worker.java:121)
> at
> org.apache.kafka.connect.runtime.AbstractHerder.startServices(AbstractHerder.java:95)
> at
> org.apache.kafka.connect.runtime.distributed.DistributedHerder.run(DistributedHerder.java:193)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [Thread-1] INFO org.apache.kafka.connect.runtime.Connect - Kafka Connect
> stopping
> [Thread-1] INFO org.apache.kafka.connect.runtime.rest.RestServer - Stopping
> REST server
> [Thread-2] INFO org.eclipse.jetty.server.ServerConnector - Stopped
> ServerConnector@2cab9998{HTTP/1.1}{HOST:8083}
> {code}
> any ideias ? I think this is a bug on SASL_PLAINTEXT
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
