[
https://issues.apache.org/jira/browse/KAFKA-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16094920#comment-16094920
]
Yogesh BG edited comment on KAFKA-5618 at 7/20/17 4:29 PM:
-----------------------------------------------------------
You can see it periodically sending metadata request to other nodes with empty
topics requests.. This one thing i observed. When i had 64 partitions it used
to work well... I wonder start call is not returned because after start is
called i log and do stat some other threads i see those threads are not
started...
For successful scenario u can see the log attached in the issue
https://issues.apache.org/jira/browse/KAFKA-5545
https://issues.apache.org/jira/browse/KAFKA-5593
When 9i increased the partition size to 360 with bigger capacity machines it
hanged and never able to recover.... And no error log or any logs from k streams
was (Author: yogeshbelur):
You can see it periodically sending metadata request to other nodes with empty
topics requests.. This one thing i observed. When i had 64 partitions it used
to work well... I wonder start call is not returned because after start is
called i log and do stat some other threads i see those threads are not
started...
For successful scenario u can see the log attached in the issue
> Kafka stream not receive any topic/partitions/records info
> ----------------------------------------------------------
>
> Key: KAFKA-5618
> URL: https://issues.apache.org/jira/browse/KAFKA-5618
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Yogesh BG
> Priority: Critical
> Attachments: rtp-kafkastreams2.log, rtp-kafkastreams3.log,
> rtp-kafkastreams.log
>
>
> I have 3 brokers and 3 stream consumers.
> I have there are 360 partitions and not able to bring up streams successfully
> even after several retry.
> I have attached the logs.
> There are other topics which are having around 16 partitions and they are
> able to successfully be consumed by kafka client<no streaming>
> when tried getting thread dump using jstack the process is not responding
> Attaching to process ID 10663, please wait...
> Debugger attached successfully.
> Server compiler detected.
> JVM version is 24.141-b02
> Deadlock Detection:
> java.lang.RuntimeException: Unable to deduce type of thread from address
> 0x00007fdac4009000 (expected type JavaThread, CompilerThread, ServiceThread,
> JvmtiAgentThread, or SurrogateLockerThread)
> at
> sun.jvm.hotspot.runtime.Threads.createJavaThreadWrapper(Threads.java:162)
> at sun.jvm.hotspot.runtime.Threads.first(Threads.java:150)
> at
> sun.jvm.hotspot.runtime.DeadlockDetector.createThreadTable(DeadlockDetector.java:149)
> at
> sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:56)
> at
> sun.jvm.hotspot.runtime.DeadlockDetector.print(DeadlockDetector.java:39)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
