Additional migration assistant feedback #8895
Conversation
Signed-off-by: Archer <[email protected]>
Naarcha-AWS
requested review from
kolchfa-aws,
AMoo-Miki,
natebower,
dlvenable and
epugh
as code owners
|
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
Signed-off-by: Archer <[email protected]>
Signed-off-by: Archer <[email protected]>
Signed-off-by: Archer <[email protected]>
Naarcha-AWS
changed the title
_migration-assistant/migration-phases/live-traffic-migration/index.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
|
|
||
| # Live traffic migration | ||
|
|
||
| Live traffic migration intercepts HTTP requests and stores them in a robust, expandable stream before sending them to the original cluster. It then duplicates these stored requests, sending them to both the original and new clusters. This process allows for performance testing of the new cluster, maintains synchronization between clusters, and highlights any differences between them. The system uses Kafka to manage the data flow and reconstruct the HTTP requests. Users can monitor the replication process using CloudWatch metrics and the Migration Management Console, which provides results in JSON format for easy analysis. |
There was a problem hiding this comment.
I would make small adjustments shown in the message snippet below:
Live traffic migration intercepts HTTP requests to a source cluster and stores them in a durable stream before forwarding them to the source cluster. The stored requests are then duplicated and replayed to the target cluster. This process synchronizes the source and target clusters while highlighting behavioral and performance differences between them. Kafka is used to manage the data flow and reconstruct HTTP requests. Users can monitor the replication process through CloudWatch metrics and the Migration Management Console, which provides results in JSON format for analysis.
Signed-off-by: Naarcha-AWS <[email protected]>
Naarcha-AWS
added
4 - Doc review
_migration-assistant/migration-phases/live-traffic-migration/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: kolchfa-aws <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Signed-off-by: Archer <[email protected]>
Signed-off-by: Archer <[email protected]>
* Fix migration assistant bugs Signed-off-by: Archer <[email protected]> * Fix link Signed-off-by: Archer <[email protected]> * Additional feedback Signed-off-by: Archer <[email protected]> * Add additional feedback. Signed-off-by: Archer <[email protected]> * Apply suggestions from code review Signed-off-by: Naarcha-AWS <[email protected]> * Update index.md Signed-off-by: Naarcha-AWS <[email protected]> * Update index.md Signed-off-by: Naarcha-AWS <[email protected]> * Apply suggestions from code review Co-authored-by: kolchfa-aws <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> * Fix TOC. Signed-off-by: Archer <[email protected]> * fix link Signed-off-by: Archer <[email protected]> --------- Signed-off-by: Archer <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]> Co-authored-by: kolchfa-aws <[email protected]> (cherry picked from commit befc0d2) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Fixes bugs from the first phase of Migration Assistant documentation.
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.