1 Answer
- Newest
- Most votes
- Most comments
0
Hi, debug9
When using MSK Replicator to replicate MSK topic data and consumer offset from cluster X to cluster Y, and if cluster X crashes and you recreate a new cluster with the same name X, here's how the MSK Replicator would work:
Replicator Behavior for Recreated Cluster X:
- If you recreate cluster X with the same name, MSK Replicator may not automatically resume replication to the new cluster X. MSK Replicator maintains a mapping between topics and consumer groups in the source and destination clusters. Recreating a cluster with the same name may not be automatically recognized as the same cluster by the replicator.
- You may need to update the MSK Replicator configuration to point to the new cluster X, ensuring that the replication configuration is aligned with the new cluster's details.
Creating a New MSK Replicator to Replicate Data from Cluster Y to New Cluster X:
- If you create a new MSK Replicator to replicate data from cluster Y to the new cluster X, the replicator will copy data from Y to the new cluster X as configured in the replication configuration.
- This process is independent of the previous replication from old cluster X to cluster Y.
MSK Replicator Version Compatibility:
- MSK Replicator's version compatibility depends on the versions of Apache Kafka running on the source and destination clusters.
- From my understanding, it's recommended to use MSK Replicator with clusters running the same Kafka version to ensure compatibility and proper replication.
answered a year ago
Relevant content
- asked 4 months ago
- Accepted Answerasked 5 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago