kafka-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu, Libo " <libo...@citi.com>
Subject failover strategy
Date Sat, 29 Jun 2013 00:29:29 GMT

I can think of two failover strategies. I am not sure which one is the right way to go.

First method. set up kafka server A on cluster 1 and set up another server B on cluster 2.
The two clusters are in different data centers. Use customized mirrormaker to sync between
the two servers. Use one server in production and use the other one as contingency. If
server A is down, server B will be used (this can be transparent to publishers/consumers).
There may be a lag between the two servers before server A is down . But after A is back,
the customized mirrormaker can sync the two. And eventually B will have all the data A had
before the failure.

Second method. Set up one kafka server using cluster 1 and cluster 2. When creating a topic
always use two replications. For each partition, assign one replication to a broker in cluster
and assign the other replication to a broker in cluster 2. So kafka will handle the syncing
and failover
for the two clusters. Is that a right (expected) way to use kafka?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message