Thanks Jay. We will still suffer from network latency if we use remote
write.
We probably will explore more on the idea of having local cluster and
mirror messages across the DC.
thanks,
Cal
On Wed, Jul 10, 2013 at 12:04 PM, Jay Kreps wrote:
> To publish to a remote data center just configure
To publish to a remote data center just configure the producers with the
host/port of the remote datacenter. To ensure good throughput you may want
to tune the socket send and receive buffers on the client and server to
avoid small roundtrips:
http://en.wikipedia.org/wiki/Bandwidth-delay_product
-
Thanks Jay. I thought of using the worldview architecture you suggested.
But since our consumers are also globally deployed, which means any new
messages arrive the worldview needs to be replicated back to the local DCs,
making the topology a bit complicated.
Would you please elaborate on the remo
Ah, good question we really should add this to the documentation.
We run a cluster per data center. All writes always go to the data-center
local cluster. Replication to aggregate clusters that provide the "world
wide" view is done with mirror maker.
It is also fine to write to or read from a kaf
Folks,
Our application has multiple producers globally (region1, region2,
region3). If we group all the brokers together into one cluster, we notice
an obvious network latency if a broker replicates regionally with the
request.required.acks = -1.
Is there any best practice for combating the
