valid hostname, and if not, then it breaks the loop and checks if it sent 100,000 requests. import requests import json url = 'http://localhost:14200/api/vtctlds' j = 0 for i in range(100000): x = requests com/vitessio/vitess/blob/137cf9daf41112a553f617c66a56fd8b06fad20b/go/ vt/servenv/servenv.go#L33 package servenv import ( // register the HTTP handlers for profiling _ "net/http/pprof" "net/url" "os" "os/signal" "runtime/debug"

ways. Some do it for all connections it uses, and some do it only for specific workloads, such as import, installation, etc. To support these use cases, Vitess needs to allow SET statements to be set on API This is how you would turn on the skew detection and alignment feature in a VStream client: import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew following features drive this refactor, in order of priority: • Multi-schema • VTShovel: multiple data import sources for vreplication • VTDirect: allow VTGate to directly send queries to mysql Beyond these

ways. Some do it for all connections it uses, and some do it only for specific workloads, such as import, installation, etc. To support these use cases, Vitess needs to allow SET statements to be set on This is how you would turn on the skew detection and alignment feature in a VStream client: 53 import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew following features drive this refactor, in order of priority: • Multi-schema • VTShovel: multiple data import sources for vreplication • VTDirect: allow VTGate to directly send queries to mysql Beyond these

ways. Some do it for all connections it uses, and some do it only for specific workloads, such as import, installation, etc. To support these use cases, Vitess needs to allow SET statements to be set on This is how you would turn on the skew detection and alignment feature in a VStream client: 78 import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew following features drive this refactor, in order of priority: • Multi-schema • VTShovel: multiple data import sources for vreplication • VTDirect: allow VTGate to directly send queries to mysql Beyond these

ways. Some do it for all connections it uses, and some do it only for specific workloads, such as import, installation, etc. To support these use cases, Vitess needs to allow SET statements to be set on following features drive this refactor, in order of priority: • Multi-schema • VTShovel: multiple data import sources for vreplication • VTDirect: allow VTGate to directly send queries to mysql Beyond these extends VReplication to allow a user to specify an external mysql as the source. This can be used to import data and also keep the targets up-to-date as the source is written to. VTShovel currently has two

database using go-mydumper or possibly mysqldump 1. Apply some simple transformations on the output 1. Import the data into Vitess via the frontend 1. Repoint your application to the new database 1. Resume writing summary of some potential options are: “Stop the world”: • Write application-level tools to export, import, and verify data between the source and destination systems. Dual writes: • Modify the application