may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay from master to replica(s). Related Vitess Documentation global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell to be at a transaction boundary. But a file:position based binlog can report a position for every event, including stray ones that are not material for replication. In such cases, the mechanism of getting

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay from master to replica(s). Related Vitess Documentation global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell to be at a transaction boundary. But a file:position based binlog can report a position for every event, including stray ones that are not material for replication. In such cases, the mechanism of getting

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay from primary to replica(s). Related Vitess Documentation global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell to be at a transaction boundary. But a file:position based binlog can report a position for every event, including stray ones that are not material for replication. In such cases, the mechanism of getting

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay from master to replica(s). Related Vitess Documentation global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell to be at a transaction boundary. But a file:position based binlog can report a position for every event, including stray ones that are not material for replication. In such cases, the mechanism of getting

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay. Related Vitess Documentation • MoveTables User Guide global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell steps: 1. It finds shards that belong to the keyspace, including newly added shards if a resharding event has taken place. 2. It validates the SQL syntax and determines the impact of the schema change. If

global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell steps: 1. It finds shards that belong to the keyspace, including newly added shards if a resharding event has taken place. 2. It validates the SQL syntax and determines the impact of the schema change. If Description include_event_token bool This used to be exclude_field_names, which was replaced by IncludedFields enum below If set, we will try to include an EventToken with the responses. compare_event_token EventToken

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay from master to replica(s). Related Vitess Documentation global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell the specified snapshot_time timestamp, vttablet needs to find the GTID corresponding to the last event before this timestamp from the binlog server. This is an expensive operation and may take some time

may be briefly unavailable. This unavailability is usually a few seconds, but will be higher in the event that your system has a high replication delay. Related Vitess Documentation • MoveTables User Guide global topology service should have nodes in multiple cells, with enough to maintain quorum in the event of a cell failure. Local Topology Each local topology contains information related to its own cell steps: 1. It finds shards that belong to the keyspace, including newly added shards if a resharding event has taken place. 2. It validates the SQL syntax and determines the impact of the schema change. If