Unfortunately, that’s not the way Kafka works wrt Consumers. When a partition
is replicated, only one replica is the Leader — all reads and writes are done
via the Leader. The other replicas are Followers; their only job is to keep up
with the Leader. No read requests from Consumers go to Follow
Hi,
Yeah I am aware of MirrorMaker. We tried to simplify our architecture so as
to avoid needing to use MirrorMaker and just rely on the rack replication
for cross datacenter replication. I think the only missing piece to this is
making consumers only read from a subset of the nodes in the cluster,
AFAIK (not actually using myself), for cross DC replication people tend to
use MirrorMaker to transfer one cluster's data to another, usually a kind
of central DC that unifies all "regional" DCs, but the layout depends on
your business reqs.
Then your consumer are assigned only with local brokers'
Hi,
In kafka 0.10 is there a way to configure the consumer such that it is rack
aware? We replicate data across all our 'racks' and want consumers to
choose brokers that are rack local whenever possible. Our configured racks
are actually in different datacenters so there is much higher network cost
