Hi,
Thanks for your replying. I did not make a thread dump, if it happen
again I’ll dump the thread stack.
————————
舒琦
地址：长沙市岳麓区文轩路27号麓谷企业广场A4栋1单元6F
网址：http://www.eefung.com
微博：http://weibo.com/eefung
邮编：410013
电话：400-677-0986
传真：0731-88519609
> 在 2017年2月7日，23:52，Jagadish Venkatraman <jagadish1...@gmail.com> 写道：
>
> >> all the task can’t fetch any messages any more, even after restarted the
> >> samza job
>
> Some questions:
>
> Are you observing an exception in the logs?
> Are you able to consume the messages using a simple consumer?
> Is Samza hanging on the call to fetch?
>
> A thread dump of the impacted container is helpful.
>
> Cheers,
> Jag
>
>
>
>
> On Mon, Feb 6, 2017 at 11:28 PM, 舒琦 <sh...@eefung.com
> <mailto:sh...@eefung.com>> wrote:
> Hi,
>
> During the running of Samza, one of brokers in our Kafka cluster went
> down, the states of relative topics are shown as pictures below. Then all the
> task can’t fetch any messages any more, even after restarted the samza job.
> But at the same time , another app consuming the same topic which using high
> level api can still fetch messages as before.
> After delete the relative topics and the broker went down was up again,
> the samza job can fetch messages as normal.
> Thanks for your help.
>
>
> ————————
> ShuQi
>
>
>
> --
> Jagadish V,
> Graduate Student,
> Department of Computer Science,
> Stanford University
