artition, so you don't have to worry about them repeating work.
>
> Hope this helps.
> Eno
>
> > On 25 Aug 2016, at 16:50, Abhishek Agarwal <abhishc...@gmail.com> wrote:
> >
> > Hi,
> > I was reading up on kafka streams for a project and came across this bl
sumes the output
> from the upstream application)
>
>
> -Matthias
>
> On 08/25/2016 07:45 PM, Eno Thereska wrote:
> > Good question. All of them would run in a single thread. That is the
> model. Multiple threads would make sense to run separate DAGs.
> >
> > Eno
kafka connect to transfer data from kafka to any external store?
- No support for asynchronous processing - Can I use more threads than
number of partitions for processors without sacrificing at-least once
guarantees?
--
Regards,
Abhishek Agarwal
le to
> find mbean "kafka.log:type=LogFlushStats,name=LogFlushRateAndTimeMs"
> Am I missing anything?
>
> I have set up the log flush time as 60000
>
> Thanks,
>
--
Regards,
Abhishek Agarwal
and then move it
> > back to 1 2 3 once 1 is back up. But that's a bunch of work you've have
> to
> > do yourself.
>
>
> We don't actually want this behavior, but we thought this would explain
> what we're seeing with the under-replicated partitions JMX metric. If the
> partitions aren't being moved (which makes sense), then it makes sense that
> it would claim that the partition is under-replicated, because, well, it
> is, at least briefly.
>
>
> >
> >
> -James
> >
> >
> Thanks!
>
> -Jack
>
--
Regards,
Abhishek Agarwal
On Sun, Jul 16, 2017 at 8:32 PM, Abhishek Agarwal <abhishc...@gmail.com>
wrote:
> What is the behaviour in 0.10.x if kafka producer is not able to reach any
> of the broker for a brief duration?
>
> From what I understand from the code, all the nodes will be in
> disc
