Thanks so much, I'll try.
On Mon, Aug 22, 2016 at 6:26 AM, Yi Pan wrote:
> Hi, Sining,
>
> This is a known bug that is fixed in 0.10.1 (SAMZA-911). Please try to
> upgrade to 0.10.1.
>
> Thanks!
>
> -Yi
>
> On Sun, Aug 21, 2016 at 5:55 AM, 李斯宁 wrote:
>
> > I have tried restart every kafka serve
Hi, Sining,
This is a known bug that is fixed in 0.10.1 (SAMZA-911). Please try to
upgrade to 0.10.1.
Thanks!
-Yi
On Sun, Aug 21, 2016 at 5:55 AM, 李斯宁 wrote:
> I have tried restart every kafka server. The container did not recover.
>
> log have something below:
>
> 2016-08-21 20:08:21 [WARN
I have tried restart every kafka server. The container did not recover.
log have something below:
2016-08-21 20:08:21 [WARN ](o.a.s.s.k.KafkaSystemProducer :66 )
Retrying send messsage due to RetriableException -
org.apache.kafka.common.errors.NotLeaderForPartitionException: This server
is
at the last of the container's log, prints these:
2016-08-21 19:57:01 [WARN ](o.a.s.s.k.KafkaSystemProducer :66 )
Retrying send messsage due to RetriableException -
org.apache.kafka.common.errors.NotLeaderForPartitionException: This
server is not the leader for that topic-partition.. Turn on
hi, guys
I'm using samza in realtime process. After running for about 10 hours, some
containers paused and not processing.
When I looked into the log, I found a lot of
2016-08-21 10:03:07 [WARN ](o.a.k.c.p.i.Sender :257)
Got error produce response with correlation id 490345 on
top
