*vtadminpb.GetClustersRequest) (*vtadminpb.GetClustersResponse, error) { span, _ := trace.NewSpan(ctx, "API.GetClusters") defer span.Finish() clusters, _ := api.getClustersForRequest(nil) vcs := make([]*vtadminpb error) { span, ctx := trace.NewSpan(ctx, "VtctldServer.GetBackups") defer span.Finish() defer panicHandler(&err) span.Annotate("keyspace", req.Keyspace) span.Annotate("shard", req.Shard) span.Annotate("limit" Annotate("limit", req.Limit) span.Annotate("detailed", req.Detailed) span.Annotate("detailed_limit", req.DetailedLimit) bs, err := backupstorage.GetBackupStorage() if err != nil { return nil, err } defer bs

transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended sent to the server). In the example, this option is set to zero, because we will be passing custom span contexts to the queries we want to trace. In this way, we only instrument the queries we want. This

cut-over and termination of the VReplication stream. It is possible for a VReplication migration to span multiple tablets, detailed below. In this case, if the tablet goes down, then the migration will not run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This

run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This sent to the server). In the example, this option is set to zero, because we will be passing custom span contexts to the queries we want to trace. In this way, we only instrument the queries we want. This

run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This sent to the server). In the example, this option is set to zero, because we will be passing custom span contexts to the queries we want to trace. In this way, we only instrument the queries we want. This

run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This sent to the server). In the example, this option is set to zero, because we will be passing custom span contexts to the queries we want to trace. In this way, we only instrument the queries we want. This

run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This

run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This

transaction that tries to go beyond a single database will fail. 2. Multi database: A transaction can span multiple databases, but the commit will be best effort. Partial commits are possible. 3. 2PC: This run KILL from there. Cross-shard Transactions By default, Vitess does not support transactions that span across shards. While Vitess can support this with the use of Two-Phase Commit, it is usually recommended