. . . . . . . . . . . . . . . . . . 18 Common Build Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Build on macOS . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Install Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Build Vitess . . . . . . . . . . (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed: /usr/sbin/mysqld: exit status

. . . . . . . . . . . . . . . . 18 Build on CentOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Install Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Build Vitess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . currently has some additional tests written in Python, but we will be skipping this step for simplicity. 18 Disable SELinux SELinux will not allow Vitess to launch MySQL in any data directory by default. You

. . . . . . . . . . . . . . . . . 18 Insert some data into the cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Examine the data we just inserted inserted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W0520 18:05:40.443933 6824 main.go:64] W0521 01:05:40.443180 reparent.go:185] master -elect tablet zone1 -0000000100 is not the shard master, proceeding anyway as -force was used 16 W0520 18:05:40.445230

. . . . . . . . . . . . . . . . . 18 Testing your Binaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Common Build Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Code Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed: /usr/sbin/mysqld: exit status

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 18 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed: /usr/sbin/mysqld: exit status log): stat /home/morgo/vitess/vtdataroot/vt_0000000102/error.log: no such file or directory E1027 18:28:23.464117 19486 mysqlctl.go:254] failed init mysql: /usr/sbin/mysqld: exit status 1, output: mysqld:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 18 Running, tracking and controlling Online DDL . . . . . . . . . . . . . . . . . . . . . . . . . . (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed: /usr/sbin/mysqld: exit status log): stat /home/morgo/vitess/vtdataroot/vt_0000000102/error.log: no such file or directory E1027 18:28:23.464117 19486 mysqlctl.go:254] failed init mysql: /usr/sbin/mysqld: exit status 1, output: mysqld:

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 18 Non-Unique Lookup Vindexes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . (/vitess/global) [6] MySQL Fails to Initialize This error is most likely the result of SELinux enabled: 1027 18:28:23.462926 19486 mysqld.go:734] mysqld --initialize -insecure failed: /usr/sbin/mysqld: exit status log): stat /home/morgo/vitess/vtdataroot/vt_0000000102/error.log: no such file or directory E1027 18:28:23.464117 19486 mysqlctl.go:254] failed init mysql: /usr/sbin/mysqld: exit status 1, output: mysqld:

. . . . . . . . . . . . . . . 18 Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Execution Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Keyspace ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . plans can also be observed with EXPLAIN FORMAT=vitess . Related Vitess Documentation • VTGate 18 Keyspace ID The keyspace ID is the value that is used to decide on which shard a given row lives

vttablet mysqld vttablet replicas mysqld vttablet big data replicas mysqld vttablet vtctld App 18 VITESS.IO Marketplace Schema customer cid name orders oid cid pid mname merchant name product pid

ecosystem. A team of five Cure53 testers investigated the software system during a budgeted period of 18 days in February 2019. All tasks were completed in accordance with the specified testing methodology