revealed a rather limited attack surface. This observation was later confirmed as the subsequent phases of the test ensued. While the results of this assessment are few and far between and may suggest defines the scope of the test and then moves on to explaining the employed test methodology. Subsequent phases and details relevant for the test are covered next and clarify which aspects were investigated during that was used during this source code audit and penetration tests. The test was divided into two phases. Each phase had goals that were closely linked to the areas in scope. The initial phase (Phase 1)

stores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service

stores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service

stores a separate partitioning for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests different ServedFrom record for each (cell, tablet type) pair. This allows migrations to proceed in phases: first migrate rdonly and replica requests, one cell at a time, and finally migrate master requests go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: 63 • Start with the old topo service implementation we want to replace. • Bring up the new topo

using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till

using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till

Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service

using the last vgtid that it received. Architecture/Design During a copy there will two distinct phases: 1. Copy phase: where the vstreamer is sending row data in bulk using the primary key to “paginate” go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: 113 • Start with the old topo service implementation we want to replace. • Bring up the new topo Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till

go/vt/topo/helpers/tee.go. It allows communicating to two topo services, and the migration uses multiple phases: • Start with the old topo service implementation we want to replace. • Bring up the new topo service Step T4 is called Fast Forward. Catchup As detailed above the catchup phase runs between two copy phases. During the copy phase the gtid position can move significantly ahead. So we run a replicate till query of this type will be scattered across all 4 the shards, given the schema and VSchema. • The phases of the scatter operation will occur in parallel. This is because the number 1 on the left-hand-side