>> 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> 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
