. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bulk copy based mechanism similar to vreplication streams, used in MoveTables or Reshard sharding workflows. Note that with vstream copy the client vstream will not faithfully reproduce the events from the form of durability addresses the modern concerns of device failures and disasters. Many of the workflows in Vitess have been built with this approach in mind. For example, turning on semi-sync replication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . switched This document outlines the steps involved in the cutover process of MoveTables and Reshard workflows when traffic is switched from the source tables/shards to the target tables/shards. We use the resharding

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bulk copy based mechanism similar to vreplication streams, used in MoveTables or Reshard sharding workflows. Note that with vstream copy the client vstream will not faithfully reproduce the events from the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bulk copy based mechanism similar to vreplication streams, used in MoveTables or Reshard sharding workflows. Note that with vstream copy the client vstream will not faithfully reproduce the events from the

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Image Source: https://github.com/blog/2042-git-2-5-including-multiple-worktrees-and-triangular-workflows The Vitess code is hosted on GitHub (https://github.com/vitessio/vitess). This repository is called

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . form of durability addresses the modern concerns of device failures and disasters. Many of the workflows in Vitess have been built with this approach in mind. For example, turning on semi-sync replication Lifecycle subsets and configuration Different environments and users have different requirements and workflows. For example: • Some wish to immediately start purging the table, wait for pages to evacuate, then

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Workflows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . form of durability addresses the modern concerns of device failures and disasters. Many of the workflows in Vitess have been built with this approach in mind. For example, turning on semi-sync replication

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Workflows involving the Topology Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . form of durability addresses the modern concerns of device failures and disasters. Many of the workflows in Vitess have been built with this approach in mind. For example, turning on semi-sync replication using vtctl ApplyVSchema (unless prevented by flags). Workflows involving the Topology Service The Topology Service is involved in many Vitess workflows. When a Tablet is initialized, we create the Tablet

viewing the existing keyspaces. The /topology route shows the existing keyspaces correctly. The /workflows and /schemas apis get denied too, when a user creates a keyspace containing the “/” char: This