You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Matthias J. Sax (JIRA)" <ji...@apache.org> on 2017/11/22 23:54:00 UTC
[jira] [Commented] (KAFKA-6260) KafkaStream 1.0.0 does not starts
correctly with Broker 0.11.0.1
[ https://issues.apache.org/jira/browse/KAFKA-6260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16263585#comment-16263585 ]
Matthias J. Sax commented on KAFKA-6260:
----------------------------------------
I did a quick test locally but could not reproduce this: downloaded `kafka_2.12-0.11.0.1.tgz` from AK webpage. Start ZK, broker, create topics for AK WordCount example. Using current {{trunk}} I ran WordCount and it just worked. [~habdank] What is your environment that hits this issue?
> KafkaStream 1.0.0 does not starts correctly with Broker 0.11.0.1
> ----------------------------------------------------------------
>
> Key: KAFKA-6260
> URL: https://issues.apache.org/jira/browse/KAFKA-6260
> Project: Kafka
> Issue Type: Bug
> Reporter: Seweryn Habdank-Wojewodzki
>
> The new KafkaStreams API (v. 1.0.0), which uses StreamsBuilder class has troubles to connect with Broker v. 0.11.0.1.
> Below there are logs.
> The same app wich uses old API (v. 0.11.0.1) KStreamBuilder has no issues to connect with Broker 0.11.0.1.
> Can you check that?
> {code}
> 2017-11-22 16:27:58 DEBUG NetworkClient:183 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Disconnecting from node 1 due to request timeout.
> 2017-11-22 16:27:58 DEBUG ConsumerNetworkClient:195 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Cancelled FETCH request RequestHeader(apiKey=FETCH, apiVersion=5, clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, correlationId=74) with correlation id 74 due to node 1 being disconnected
> 2017-11-22 16:27:58 DEBUG Fetcher:195 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Fetch request {my_internal_topic-4=(offset=199966200, logStartOffset=-1, maxBytes=1048576), my_internal_topic-0=(offset=199987332, logStartOffset=-1, maxBytes=1048576)} to myp01.eb.lan.at:9093 (id: 1 rack: DC-1) failed org.apache.kafka.common.errors.DisconnectException: null
> 2017-11-22 16:27:58 DEBUG NetworkClient:183 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Initialize connection to node myp01.eb.lan.at:9093 (id: 1 rack: DC-1) for sending metadata request
> 2017-11-22 16:27:58 DEBUG NetworkClient:183 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Initiating connection to node myp01.eb.lan.at:9093 (id: 1 rack: DC-1) 2017-11-22 16:27:58 ERROR AbstractCoordinator:296 - [Consumer clientId=kafka-endpoint-1a02a283-47e0-40b6-8da4-6e338da0814f-StreamThread-1-consumer, groupId=kafka-endpoint] Heartbeat thread for group kafka-endpoint failed due to unexpected errorjava.lang.NullPointerException: null
> at org.apache.kafka.common.network.Selector.pollSelectionKeys(Selector.java:436) ~[my-kafka-endpoint.jar:?]
> at org.apache.kafka.common.network.Selector.poll(Selector.java:395) ~[my-kafka-endpoint.jar:?]
> at org.apache.kafka.clients.NetworkClient.poll(NetworkClient.java:460) ~[my-kafka-endpoint.jar:?]
> at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.poll(ConsumerNetworkClient.java:238) ~[my-kafka-endpoint.jar:?]
> at org.apache.kafka.clients.consumer.internals.ConsumerNetworkClient.pollNoWakeup(ConsumerNetworkClient.java:275) ~[my-kafka-endpoint.jar:?]
> at org.apache.kafka.clients.consumer.internals.AbstractCoordinator$HeartbeatThread.run(AbstractCoordinator.java:934) [my-kafka-endpoint.jar:?]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)