-set_serial 01 -out server-cert.pem The output of the above command (for example): Signature ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiKV, CN = TiKV Test Server k@pingcap.com Getting CA Private Key Note: When you log in, TiDB checks whether the information in the subject section of the above output is consistent or not. 12.10.5.1.3 Generate client key and certificate ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiDB, CN = tpch-user1, emailAddress = zz@pingcap.com Getting CA Private Key Note: The information of the subject section

-set_serial 01 -out server-cert.pem The output of the above command (for example): Signature ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiKV, CN = TiKV Test Server k@pingcap.com Getting CA Private Key Note: When you log in, TiDB checks whether the information in the subject section of the above output is consistent or not. 12.10.5.1.3 Generate client key and certificate ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiDB, CN = tpch-user1, emailAddress = zz@pingcap.com Getting CA Private Key Note: The information of the subject section

-set_serial 01 -out server-cert.pem The output of the above command (for example): Signature ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiKV, CN = TiKV Test Server k@pingcap.com Getting CA Private Key Note: When you log in, TiDB checks whether the information in the subject section of the above output is consistent or not. 12.10.5.1.3 Generate client key and certificate ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiDB, CN = tpch-user1, emailAddress = zz@pingcap.com Getting CA Private Key Note: The information of the subject section

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before operations during the upgrade process. After the smooth upgrade feature is introduced, TiDB is no longer subject to this limitation during the upgrade process. For more information, see the Warning content in = @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. 2407 [ alt_names ]

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before operations during the upgrade process. After the smooth upgrade feature is introduced, TiDB is no longer subject to this limitation during the upgrade process. For more information, see the Warning content in = @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. [ alt_names ] IP.1 =

= @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. 1683 [ alt_names ] -set_serial 01 -out server-cert.pem The output of the above command (for example): Signature ok subject=C = US, ST = California, L = San Francisco, O = PingCAP Inc., �→ OU = TiKV, CN = TiKV Test Server k@pingcap.com Getting CA Private Key Note: When you log in, TiDB checks whether the information in the subject section of the above output is consistent or not. 12.10.5.1.3 Generate client key and certificate

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before operations during the upgrade process. After the smooth upgrade feature is introduced, TiDB is no longer subject to this limitation during the upgrade process. For more information, see the Warning content in = @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. 2428 [ alt_names ]

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before operations during the upgrade process. After the smooth upgrade feature is introduced, TiDB is no longer subject to this limitation during the upgrade process. For more information, see the Warning content in = @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. 2461 [ alt_names ]

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before TiCDC replication speed, the metric might be extremely large. Because TiCDC replication speed is subject to many factors, this metric is for reference only and might not be the actual replication time. only takes effect if the downstream is MQ. ### schema-registry = "http://localhost:80801/subjects/{subject-name}/ �→ versions/{version-number}/schema" ### Specifies the number of encoder threads used when

yet (experimental) and you need to be aware of the usage limitations. Experimental features are subject to change or removal without prior notice. The syntax and implementation might be modified before operations during the upgrade process. After the smooth upgrade feature is introduced, TiDB is no longer subject to this limitation during the upgrade process. For more information, see the Warning content in = @alt_names under the [ v3_req ] field. Finally, create a new field and edit the information of Subject Alternative Name (SAN) according to the cluster topology description above. 2622 [ alt_names ]