Hi Stephen, Hans,

This can help in keeping the traffic isolated in an availability zone, and
avoid inter AZ communication.

Thanks,
Mohit

On Thursday, August 24, 2017, Hans Jespersen <h...@confluent.io> wrote:

> We (Confluent) run Kafka as a SaaS-based cloud offering and we do not see
> any reason for this feature so I just don’t understand the motivation for
> it. Please explain.
>
> -hans
>
> --
> /**
>  * Hans Jespersen, Principal Systems Engineer, Confluent Inc.
>  * h...@confluent.io <javascript:;> (650)924-2670
>  */
>
>
>
>
> > On Aug 23, 2017, at 12:42 AM, Mohit Chawla <
> mohit.chawla.bin...@gmail.com <javascript:;>> wrote:
> >
> > Hey Hans,
> >
> > Thanks for your reply.
> >
> > In a cloud environment this can be useful. Perhaps if partitioning and
> > replicas are selected appropriately, this could be possible ?
> >
> > Thanks,
> > Mohit
> >
> > On Tuesday, August 22, 2017, Hans Jespersen <h...@confluent.io
> <javascript:;>> wrote:
> >
> >> Doing that doesn't really make sense in a Kafka cluster because the
> topic
> >> partitions and their replicas are spread out across many brokers in the
> >> cluster. That's what enables the parallel processing and fault tolerance
> >> features of Kafka.
> >>
> >> -hans
> >>
> >>> On Aug 22, 2017, at 3:14 AM, Mohit Chawla <
> mohit.chawla.bin...@gmail.com <javascript:;>
> >> <javascript:;>> wrote:
> >>>
> >>> Hi folks,
> >>>
> >>> Is it possible to pin kafka clients to use only specific brokers
> >> throughout
> >>> their lifetime and not just for the initial bootstrapping ?
> >>>
> >>> Thanks,
> >>> Mohit
> >>
>
>

Reply via email to