Bielefelder Str. 14 D 10709 Berlin cure53.de · mario@cure53.de Pentest-Report Vitess 02.2019 Cure53, Dr.-Ing. M. Heiderich, M. Wege, MSc. N. Krein, MSc. D. Weißer, J. Larsson Index Introduction Mario Heiderich, Cure53 Bielefelder Str. 14 D 10709 Berlin cure53.de · mario@cure53.de dedicated instant messaging channel was used for arising questions and further Mario Heiderich, Cure53 Bielefelder Str. 14 D 10709 Berlin cure53.de · mario@cure53.de Test Methodology This section describes the methodology that was used during this source

keyspace has effectively one shard. Vitess names the shard 0 by convention. When sharded, a keyspace has N shards with non-overlapping data. Shard Naming Shard names have the following characteristics: • pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

keyspace has effectively one shard. Vitess names the shard 0 by convention. When sharded, a keyspace has N shards with non-overlapping data. Shard Naming Shard names have the following characteristics: • pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

keyspace has effectively one shard. Vitess names the shard 0 by convention. When sharded, a keyspace has N shards with non-overlapping data. Shard Naming Shard names have the following characteristics: • pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

single shard. Vitess names the shard 0 (or sometimes -) by convention. When sharded, a keyspace has N shards with non-overlapping data. The number of shards in a keyspace can vary depending on the use-case pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

single shard. Vitess names the shard 0 (or sometimes -) by convention. When sharded, a keyspace has N shards with non-overlapping data. The number of shards in a keyspace can vary depending on the use-case pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

single shard. Vitess names the shard 0 (or sometimes -) by convention. When sharded, a keyspace has N shards with non-overlapping data. The number of shards in a keyspace can vary depending on the use-case pods NAME READY STATUS RESTARTS AGE example -etcd-faf13de3 -1 1/1 Running 0 78s example -etcd-faf13de3 -2 1/1 Running 0 78s example -etcd-faf13de3 -3 1/1 Running 0 78s example -vttablet -zone1 -2469782763-bfadd780 front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight

pass a value that could traverse the storage. https://github.com/vitessio/vitess/blob/aa87bc4e9f05e3de3955e9641799eca9114d83bb/g o/vt/vtctl/grpcvtctldserver/server.go#L1161 func (s *VtctldServer) GetBackups(ctx Sprintf("Uid: %v
\nSource: %v/%v
\n", source.Uid, source.Keyspace, source.Shard) if key.KeyRangeIsPartial(source.KeyRange) { result += fmt.Sprintf("KeyRange: %v-%v
\n", hex.EncodeToString(source EncodeToString(source.KeyRange.End)) } if len(source.Tables) > 0 { result += fmt.Sprintf("Tables: %v
\n", strings.Join(source.Tables, " ")) } return template.HTML(result) } https://github.com/vitessi

keyspace has effectively one shard. Vitess names the shard 0 by convention. When sharded, a keyspace has N shards with non-overlapping data. Shard Naming Shard names have the following characteristics: • front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight transaction is committed). • MySQL has multiple options for auto-increment, like only using every N number (for multi-master configurations), or performance related features (locking that table’s current

keyspace has effectively one shard. Vitess names the shard 0 by convention. When sharded, a keyspace has N shards with non-overlapping data. Resharding Vitess supports dynamic resharding, in which the number Vitess can use to generate monotonically increasing ids. The syntax to generate an id is: select next :n values from customer_seq. The vttablet that exposes this table is capable of serving a very large number front-end application queries onto a pool of MySQL connections to optimize perfor- mance. – Query de-duping – Reuse results of an in-flight query for any identical requests received while the in-flight