> > Out of curiosity - what's the typical latency (distribution) you see > between zones? > > Unfortunately I don't have any good numbers on that. Since we're publishing > both in the same AZ and to other AZs the latency metrics reflect both. If I > figure out a good way to measure this I will report back.
Thanks - I was wondering if you had done some simple ping/traceroute tests. It's just that with replicas in different zones the end-to-end latency from producer to consumer will be correspondingly higher. Does your zookeeper setup span zones as well? > > On Tue, May 26, 2015 at 10:44 PM, Joel Koshy <jjkosh...@gmail.com> wrote: > > > > Apologies if this question has been asked before. If I understand things > > > correctly a client can only fetch from the leader of a partition, not > > from > > > an (in-sync) replica. I have a use case where it would be very beneficial > > > if it were possible to fetch from a replica instead of just the leader, > > and > > > I wonder why it is not allowed? Are there any consistency problems with > > > allowing it, for example? Is there any way to configure Kafka to allow > > it? > > > > Yes this should be possible. I don't think there are any consistency > > issues (barring any bugs) since we never expose past the > > high-watermark and the follower HW is strictly <= leader HW. Can you > > file a jira for this? > > > > > The use case is a Kafka cluster running in EC2 across three availability > > > zones. > > > > Out of curiosity - what's the typical latency (distribution) you see > > between zones? > > > > Joel > >
