generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 41
Open
Labels
Description
What is the bug?
See this issue where a user had an RFS migration that took > 200 RFS check iterations to finish. There was an overflow issue in Argo Workflows when computing the wait durationthat would have caused these checks to happen much more often. However, even independent of that, RFS migrations could take a very long time. We should bump that default up AND allow users to override that value.
What are your migration environments?
What version of the Migration Assistant (this can be determined by running console --version on the Migration Console).
EKS releases: 2.6+ and
How can one reproduce the bug?
Configure one podReplica for RFS, set the parameters to send very slowly. Wait until the checks give up.
What is the expected behavior?
That even a slow RFS migration will complete.
Reactions are currently unavailable