CCAAK · Question #59
Your organization has a mission-critical Kafka cluster that must be highly available. A Disaster Recovery (DR) cluster has been set up using Replicator, and data is continuously being replicated…
The correct answer is C. The offsets for the messages on the source, destination cluster may not match. When using Confluent Replicator (or MirrorMaker), offsets are not preserved between the source and destination Kafka clusters. Messages are replicated based on content, but they are assigned new offsets in the DR (destination) cluster. Therefore, offset 1002 on the source and…
Question
Your organization has a mission-critical Kafka cluster that must be highly available. A Disaster Recovery (DR) cluster has been set up using Replicator, and data is continuously being replicated from source cluster to the DR cluster. However, you notice that the message on offset 1002 on source cluster does not seem to match with offset 1002 on the destination DR cluster. Which statement is correct?
Options
- AThe DR cluster is lagging behind updates; once the DR cluster catches up, the messages will
- BThe message on DR cluster got over-written accidently by another application.
- CThe offsets for the messages on the source, destination cluster may not match.
- DThe message was updated on source cluster, but the update did not flow into destination DR
How the community answered
(30 responses)- A10% (3)
- B17% (5)
- C70% (21)
- D3% (1)
Explanation
When using Confluent Replicator (or MirrorMaker), offsets are not preserved between the source and destination Kafka clusters. Messages are replicated based on content, but they are assigned new offsets in the DR (destination) cluster. Therefore, offset 1002 on the source and offset 1002 on the DR cluster likely refer to different messages, which is expected behavior.
Topics
Community Discussion
No community discussion yet for this question.