committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the apply -f operator.yaml Bring up an initial cluster In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the

committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the records, and the local SrvKeyspace records. Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations:

committing. 19 • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. ∗ Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the records, and the local SrvKeyspace records. 62 Exploring the data in a Topology Service We store the proto3 serialized binary data for each object. We use the following paths for the data, in all implementations:

NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: com:vitessio/vitess.git cd vitess/examples/helm In this directory, you will see a group of yaml files. The first digit of each file name indicates the phase of example. The next two digits indicate the

NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: able to specify parameters for a thousand tablet servers is not going to be practical. Using config files is a better option. To prevent verbosity, we can use a hierarchy where the root config specifies initial

NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp 23 System variable Handled long_query_time NoOp low_priority_updates committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: skew detection and alignment feature in a VStream client: import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew = true; reader , err := conn

NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: detection and alignment feature in a VStream client: 53 import vtgatepb "vitess.io/vitess/go/vt/proto/vtgate" ... ... flags := &vtgatepb.VStreamFlags{}; flags.MinimizeSkew = true; reader , err := conn

NoOp innodb_support_xa NoOp innodb_table_locks NoOp innodb_tmpdir NoOp join_buffer_size NoOp keep_files_on_create NoOp lc_messages NoOp long_query_time NoOp low_priority_updates NoOp max_delayed_threads committing. • Scan the diffs as if you’re the reviewer. – Look for files that shouldn’t be checked in (temporary/generated files). – Look for temporary code/comments you added while debugging. – Example: then the following command should be run in the root Vitess directory to update all the generated files. make codegen Release Notes description: Everything you need to know to contribute to the release

https://code.google.com/p/vitess/ • https://github.com/youtube/vitess • http://vitess.googlecode.com/files/Vitess_Percona_2012.pdf • http://vdisk.weibo.com/s/7JmTtKze0rn?from=page_100505_profile&wvr=6 Thank

We used the following sources for the threat modelling: ● Vitessʼs documentation including README files from the Vitess repository ● Vitessʼs source code at https://github.com/vitessio/vitess ● Feedback