Traffic migration switches the request routing between the versions within a service of your application, moving traffic from one or more versions to a single new version.
Traffic is migrated immediately between your versions in the flexible environment. Unlike versions in the standard environment, gradual traffic migration is not supported in the flexible environment.
If you immediately migrate traffic to a new version without any running instances then your app will have a spike in latency while instances are being created. You can avoid a spike in latency by using the App Engine Admin API to provision sufficient instances of the new app's version before you migrate traffic to it.
for the new version to the number needed to handle expected traffic. After
migration is complete, you can reset this field so that autoscaling occurs
if traffic drops.
You can split traffic between versions of your app, increasing the amount of traffic a version receives in stages.
For information about splitting traffic between two or more versions of your app, see Traffic Splitting.
Before you begin
Before you can configure traffic to a version, ensure that your user account includes the required privileges.
Migrating traffic to a new version
To migrate traffic in the Google Cloud console, go to the Versions page:
- Select the version to which you want to migrate 100% of the traffic.
- Click Migrate traffic.
- Optional: When warmup requests are enabled your traffic is migrated gradually. To migrate traffic immediately, select the option under the Show advanced options section.
To migrate traffic immediately:
gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION]=1
To gradually migrate traffic, you include the optional
gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION]=1 --migrate
To programmatically migrate traffic, you can use the Admin API, see Migrating and Splitting Traffic for details.