[ 
https://issues.apache.org/jira/browse/KAFKA-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507577#comment-16507577
 ] 

Matthias J. Sax commented on KAFKA-6976:
----------------------------------------

Just cycling back to this (also saw, that you replied to KAFKA-6631). Seems 
that both are related.

I had a look into the logs, and Streams dies when the leader tries to send a 
sync-group request, ie, when it sends the computed assignment to the broker. 
The broker stores this assignment in the __consumer_offset topics and seems to 
fail with RecordTooLargeException.

Note, that `104857600` is 100MB (this comment is with regard to your comment on 
KAFKA-6631). Seems to be some network buffer you exceed – I am not very 
familiar with broker code, so I can't tell atm. Unclear to me what `1195725856` 
is – this is indeed larger than 1GB.

Have you tried to increase the message size and after that you get the second 
error? Or did the second error also occur originally?

> Kafka Streams instances going in to DEAD state
> ----------------------------------------------
>
>                 Key: KAFKA-6976
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6976
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Deepak Goyal
>            Priority: Blocker
>         Attachments: kafkaStreamsDeadState.log
>
>
> We are using Kafka 0.10.2.0, Kafka-Streams 1.1.0. We have Kafka Cluster of 16 
> machines, and topic that is being consumed by Kafka Streams has 256 
> partitions. We spawned 400 machines of Kakfa Streams application. We see that 
> all of the StreamThreads go in to DEAD state.
> {quote}{{[2018-05-25 05:59:29,282] INFO stream-thread 
> [ksapp-19f923d7-5f9e-4137-b79f-ee20945a7dd7-StreamThread-1] State transition 
> from PENDING_SHUTDOWN to DEAD 
> (org.apache.kafka.streams.processor.internals.StreamThread) [2018-05-25 
> 05:59:29,282] INFO stream-client [ksapp-19f923d7-5f9e-4137-b79f-ee20945a7dd7] 
> State transition from REBALANCING to ERROR 
> (org.apache.kafka.streams.KafkaStreams) [2018-05-25 05:59:29,282] WARN 
> stream-client [ksapp-19f923d7-5f9e-4137-b79f-ee20945a7dd7] All stream threads 
> have died. The instance will be in error state and should be closed. 
> (org.apache.kafka.streams.KafkaStreams) [2018-05-25 05:59:29,282] INFO 
> stream-thread [ksapp-19f923d7-5f9e-4137-b79f-ee20945a7dd7-StreamThread-1] 
> Shutdown complete 
> (org.apache.kafka.streams.processor.internals.StreamThread)}}
> {quote}
> Please note that when we only have 100 kafka-streams application machines, 
> things are working as expected. We see that instances are consuming messages 
> from topic.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to