Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> Combating network latency best practice


Copy link to this message
-
Combating network latency best practice
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 network latency in the
deployment topology? Should we segregate the brokers regionally (one kafka
cluster per region) and set up MirrorMaker between the regions (region1
<--> region2, region2 <--> region3, region1 <--> region3), total of 6
mirror makes?
Thanks.

 
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB