Hi ShuQi, If you suspect the container is not making progress, A thread dump of the impacted container is super-helpful to debug this further. Can you please share thread dumps?
On Wed, Mar 22, 2017 at 6:03 PM, 舒琦 <sh...@eefung.com> wrote: > Hi, > > I’m using samza 0.12 and kafka 0.10. after running for several > days, one of our job was restarted and it seems stuck in the “Get latest > offset”. > And after almost 30 minutes, it still stuck there. > > 2017-03-23 08:24:04.503 [main] KafkaUtil [INFO] Successfully validated > topic __samza_checkpoint_ver_1_for_canal-doc-content-distinct_1. > 2017-03-23 08:24:04.508 [main] KafkaCheckpointManager [INFO] Reading > checkpoint for taskName Partition 3 > 2017-03-23 08:24:04.510 [main] KafkaCheckpointManager [INFO] No TaskName > to checkpoint mapping provided. Reading for first time. > 2017-03-23 08:24:04.529 [main] KafkaCheckpointManager [INFO] Connecting to > leader 172.19.105.22:9096 for topic > __samza_checkpoint_ver_1_for_canal-doc-content-distinct_1 > and to fetch all checkpoint messages. > 2017-03-23 08:24:04.547 [main] KafkaCheckpointManager [INFO] Got offset 0 > for topic __samza_checkpoint_ver_1_for_canal-doc-content-distinct_1 and > partition 0. Attempting to fetch messages for checkpoint log. > 2017-03-23 08:24:04.557 [main] KafkaCheckpointManager [INFO] Get latest > offset 27175607 for topic > __samza_checkpoint_ver_1_for_canal-doc-content-distinct_1 > and partition 0. > > Can anyone help, thanks. > > > ———————— > ShuQi > > -- Jagadish V, Graduate Student, Department of Computer Science, Stanford University
