The Vitess 8.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with use. – grpc_ca (optional): client cert chains to trust. If specified, the client must then use a certificate signed by one of the CA certs in the provided file. • A Vitess go client can be configured with key to use to connect -tablet_grpc_server_name string the server name to use to validate server certificate -tablet_manager_grpc_ca string the server ca to use to validate servers when connecting -tablet_manager_grpc_cert0 码力 | 331 页 | 1.35 MB | 1 年前3
The Vitess 9.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered0 码力 | 417 页 | 2.96 MB | 1 年前3
The Vitess 7.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command to use. – grpc_ca (optional): client cert chains to trust. If specified, the client must use a certificate signed by one ca in the provided file. • A Vitess go client can be configured with symmetrical0 码力 | 254 页 | 949.63 KB | 1 年前3
The Vitess 6.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with configure VTGate to support TLS set -mysql_server_ssl_cert and -mysql_server_ssl_key. Client certificates can also be mandated by setting -mysql_server_ssl_ca. If there is no CA specified then TLS is optional Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command0 码力 | 210 页 | 846.79 KB | 1 年前3
The Vitess 5.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. 21 Sending Pull Requests Push your branch to the repository (and set it to track configure VTGate to support TLS set -mysql_server_ssl_cert and -mysql_server_ssl_key. Client certificates can also be mandated by setting -mysql_server_ssl_ca. If there is no CA specified then TLS is optional Transport When using gRPC transport, Vitess can use the usual TLS security features (familiarity with SSL / TLS is necessary here): • Any Vitess server can be configured to use TLS with the following command0 码力 | 206 页 | 875.06 KB | 1 年前3
The Vitess 11.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 10.0 Documentation
running git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered0 码力 | 455 页 | 3.07 MB | 1 年前3
The Vitess 12.0 Documentationrunning git commit use the -s option to add a Signed-off-by line. This is needed for the Developer Certificate of Origin. Sending Pull Requests Push your branch to the repository (and set it to track with db_charset flags: 0 # db_flags flavor: # db_flavor sslCa: # db_ssl_ca sslCaPath: # db_ssl_ca_path sslCert: # db_ssl_cert sslKey: # db_ssl_key serverName: # db_server_name connectTimeoutMilliseconds: db_app_password useSsl: true # db_app_use_ssl preferSocket: true dba: user: vt_dba # db_dba_user password: # db_dba_password useSsl: true # db_dba_use_ssl preferSocket: true filtered: user: vt_filtered0 码力 | 534 页 | 3.32 MB | 1 年前3
Vitess解析MySQL databases for large scale web services. • about 8w line(test code exclude) • client(bson SSL) java/python/go Golang ? • minimalist • goroutines • channels & selects • closures • defers0 码力 | 21 页 | 926.63 KB | 1 年前3
共 9 条
- 1













