Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/appengine/docs/legacy/standard/python/migrating-traffic below:

Migrating Traffic | App Engine standard environment for Python 2

Stay organized with collections Save and categorize content based on your preferences.

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.

For information about splitting traffic between two or more versions of your app, see Traffic Splitting.

Before you can configure traffic to a version, ensure that your user account includes the required privileges.

In the standard environment, you can choose to route requests to the target version, either immediately or gradually.

By default, warmup requests are disabled and traffic is migrated immediately to a version.

You can also choose to enable warmup requests if you want the traffic gradually migrated to a version. If you immediately migrate traffic to a new version without any running instances then you will experience a spike in latency for loading requests. Deploying a new version with the same name as an existing version causes an immediate traffic migration. All instances of the old version are immediately shut down. There will be a latency spike due to loading requests for the new version.

If warmup requests are enabled, you can migrate traffic between versions that reside in different environments only by specifying to migrate traffic immediately.

When warmup requests are enabled, traffic is migrated gradually by first sending a warmup request to new instances before those instances receive any user requests. Warmup requests improve user response time by allowing the version currently receiving traffic to handle those requests but the traffic migration to the new version can take a short amount of time while the new instances are created.

When warmup requests are not enabled, user requests are sent to those new instances before they have been created. Due to the delay caused by creating the new instances and loading application code, latency can occur for those user responses.

To avoid latency and enable warmup requests, include the

element in your configuration file before you deploy your application to App Engine.

For example, you include the following in your app.yaml file before deploying it to App Engine:

inbound_services:
- warmup

For complete details about enabling warmup requests, see Configuring Warmup Requests to Improve Performance.

To migrate traffic in the Google Cloud console, go to the Versions page:

Go to the Versions page

1. Select the version to which you want to migrate 100% of the traffic.
2. Click Migrate traffic.
3. Optional: When warmup requests are enabled your traffic is migrated gradually. To migrate traffic immediately, select the option under the Show advanced options section.

After installing the Google Cloud CLI, you run the gcloud app services set-traffic command to migrate 100% of traffic to a single version. For example:

• To migrate traffic immediately:

  gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION]=1

• To gradually migrate traffic, you include the optional --migrate flag:

  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.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["Traffic migration redirects requests from one or more existing application versions to a single, new version."],["In the standard environment, traffic migration can be immediate by default or gradual if warmup requests are enabled."],["Immediate traffic migration can lead to latency spikes due to the need to create new instances and load application code."],["Enabling warmup requests allows for a gradual traffic migration by sending warmup requests to new instances before user requests, reducing latency."],["Traffic migration to versions running in the flexible environment must be done immediately, as gradual migration is not supported there."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4