Apologies for not replying sooner. (I have digest subscription and I cannot
reply to the email chain I started! So I had not received any direct
replies either).
@Mayuresh and @Jiangjie, there was nothing very indicative in the Kafka
logs.
But I'm writing to tell you that the issue was "resolved"
What does a "clean shutdown" of the MM entail? So far I've just been using
Ctrl + C to send an interrupt to kill it.
Alex
On Sat, Mar 7, 2015 at 10:59 PM, Jiangjie Qin
wrote:
> If auto.offset.reset is set to smallest, it does not mean the consumer
> will always consume from the smallest. It me
Hey guys,
If we checked in obviously broken code on trunk, let's fix it now or revert
that change.
-Jay
On Sat, Mar 7, 2015 at 12:48 AM, Jiangjie Qin
wrote:
> Hi Tao,
>
> Thanks a lot for finding the bug. We are actually rewriting the mirror
> maker in KAFKA-1997 with a much simplified solutio
Hi Jay,
I’ve uploaded patch in KAFKA-2009 for this. It is a pretty small patch and
it will be great if you can help review it.
Thanks.
Jiangjie (Becket) Qin
On 3/8/15, 12:31 PM, "Jay Kreps" wrote:
>Hey guys,
>
>If we checked in obviously broken code on trunk, let's fix it now or
>revert
>that
Found an interesting issue that causes the slowdown of our unit tests. Not
sure how to fully explain the issue though. It would be great if someone
knows TCP and sockets well can comment on the jira :).
Thanks,
Jun
Ctrl+c is clean shutdown. kill -9 is not
On Mon, Mar 9, 2015 at 2:32 AM, Alex Melville wrote:
> What does a "clean shutdown" of the MM entail? So far I've just been using
> Ctrl + C to send an interrupt to kill it.
>
>
> Alex
>
> On Sat, Mar 7, 2015 at 10:59 PM, Jiangjie Qin
> wrote:
>
> > If a
