1 Answer
- Newest
- Most votes
- Most comments
0
Consider replicating the data in two stages - first from 2.2.1 to an intermediate upgraded cluster, then from the intermediate cluster to the 3.5.1 target. This avoids any single version jump limitations.
Export the data from the 2.2.1 source using Kafka tools like kafka-console-consumer and kafka-console-producer, then import it into the 3.5.1 target cluster. While more manual, it avoids any version incompatibilities between the source and target.
Relevant content
- asked 3 months ago
- asked a year ago
- How do I troubleshoot common issues when using my Amazon MSK cluster with SASL/SCRAM authentication?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago