OBD provides multiple-level commands. You can use the -h/--help option to view the help information of sub-commands. Similarly, you can also use -v/--verbose to view the detailed execution process of commands when the execution of sub commands reports an error.
Runs the mysqltest on the specified node of an OcecanBase cluster or ODP. To run the mysqltest, you must install OBClient.
obd test mysqltest <deploy name> [--test-set <test-set>] [flags]
# example
obd test mysqltest test --all --auto-retryThe deploy name parameter specifies the name of the deployed cluster. You can consider it as an alias for the configuration file.
This table describes the corresponding options.
| Option | Required | Data type | Default value | Description |
|---|---|---|---|---|
| --component | No | string | Empty | The name of the component to be tested. Valid values: oceanbase-ce, oceanbase, obproxy-ce and obproxy. If you do not specify a value, the existence of obproxy, obproxy-ce, oceanbase, oceanbase-ce is checked sequentially. The traversal stops when a component is found, and the component is then tested. |
| --test-server | No | string | The first node of the specified component. | Machine to be tested, followed by the name value corresponding to servers in the yaml file. If the name value is not configured after servers, the ip value is used. It must be the name of a node of the specified component. |
| --user | No | string | admin | The username for running the test. |
| --password | No | string | admin | The password for running the test. |
| --database | No | String | test | The database where the test is to be performed. |
| --mysqltest-bin | No | string | /u01/obclient/bin/mysqltest | The path of the mysqltest binary file. |
| --obclient-bin | No | string | obclient | The path of the OBClient binary file. |
| --test-dir | No | string | ./mysql_test/t | The directory that stores the test file required for the mysqltest. If no test file is found in the directory, OBD will search for a built-in test file. |
| --test-file-suffix | No | String | .test | The suffix of the test file required by mysqltest. |
| --result-dir | No | string | ./mysql_test/r | The directory that stores the result file required for the mysqltest. If no result file is found in the directory, OBD will search for a built-in result file. |
| --result-file-suffix | No | String | .result | The suffix of the result file required by mysqltest. |
| --record | No | Bool | false | Specifies whether to record only the execution results of mysqltest in the record files. |
| --record-dir | No | String | ./record | The directory where the record files that record the execution results of mysqltest are stored. |
| --record-file-suffix | No | String | .record | The suffix of the record files that record the execution results of mysqltest. |
| --tmp-dir | No | string | ./tmp | The mysqltest tmpdir option. |
| --var-dir | No | string | ./var | The directory to create the log directory. The log directory will be added to the mysqltest command as the logdir option. |
| --test-set | No | string | None | The array of test cases. Separate multiple cases with commas (,). |
| --exclude | No | String | None | The array of test cases to be excluded. Separate multiple cases with commas (,). |
| --test-pattern | No | string | None | The regular expression for matching test file names. Test cases matching the regular expression will overwrite the values of the test-set option. |
| --suite | No | string | None | The suite array. A suite contains multiple tests. Separate multiple tests with commas (,). If this option is enabled, the --test-pattern and --test-set options will become invalid. |
| --suite-dir | No | string | ./mysql_test/test_suite | The directory that stores the suite directory. If no suite directory is found in the directory, OBD will search for a built-in suite directory. |
| --all | No | bool | false | Specifies whether to run all test cases in the directory specified for the --suite-dir option. The --suite-dir option specifies the directory that stores the suite directory. |
| --need-init | No | bool | false | Specifies whether to run the init sql files. Before OBD runs the mysqltest on a new cluster, it may run some initialization files. For example, it may create some accounts or tenants required for running the test cases. The --suite-dir option specifies the directory that stores the suite directory. This option is disabled by default. |
| --init-sql-dir | No | string | ./ | The directory that stores the init sql files. If no init sql file is found in the directory, OBD will search for built-in init sql files. |
| --init-sql-files | No | string | Empty | The init sql files to be run when initialization is required. Separate multiple init sql files with commas (,). If this option is not specified but initialization is required, OBD will run the built-in init files based on the cluster configurations. |
| --auto-retry | No | bool | false | Specifies whether to automatically redeploy the cluster for a retry after a test fails. |
| --psmall | No | Bool | false | Specifies whether to execute the cases in psmall mode. |
| --slices | No | Int | Empty | The number of slices into which the case to be executed is divided. |
| --slice-idx | No | Int | Empty | The ID of the current slice. |
| --slb-host | No | String | Empty | The host for soft load balancing. |
| --exec-id | No | String | Empty | The ID of the execution. |
| --case-filter | No | String | ./mysql_test/filter.py | The filter.py file, which contains lists of cases to be filtered out. |
| --reboot-timeout | No | Int | 0 | The timeout period for the restart. |
| --reboot-retries | No | Int | 5 | The number of retries allowed if the restart fails. |
| --collect-all | No | Bool | false | Specifies whether to collect component logs. |
| --log-dir | No | String | tmp_dir/log |
The path to the directory where the mysqltest logs are stored. |
| --log-pattern | No | String | *.log | The regular expression that is used to match log file names. Files that match the expression are collected. |
| --case-timeout | No | Int | 3600 | The timeout period for a single test of mysqltest. |
| --disable-reboot | No | Bool | false | Specifies whether to disable restart during the test. |
| --collect-components | No | string | Empty | Specify the components to collect logs. Multiple components are separated by commas (,). |
| --init-only | No | bool | false | If this option is true, it means that only init SQL is executed. |
Runs the Sysbench test on the specified node of an OcecanBase cluster or ODP. To run the Sysbench test, you must install OBClient and ob-sysbench.
obd test sysbench <deploy name> [flags]
# example
sudo yum install ob-sysbench
obd test sysbench test --tenant=sysbench --script-name=oltp_read_only.lua --table-size=1000000 --threads=32 --rand-type=uniformThe deploy name parameter specifies the name of the deployed cluster. You can consider it as an alias for the configuration file.
This table describes the corresponding options.
| Option | Required | Data type | Default value | Description |
|---|---|---|---|---|
| --component | No | string | Empty | The name of the component to be tested. Valid values: oceanbase-ce, oceanbase, obproxy-ce and obproxy. If you do not specify a value, the existence of obproxy, obproxy-ce, oceanbase, oceanbase-ce is checked sequentially. The traversal stops when a component is found, and the component is then tested. |
| --test-server | No | string | The first node of the specified component. | Machine to be tested, followed by the name value corresponding to servers in the yaml file. If the name value is not configured after servers, the ip value is used. It must be the name of a node of the specified component. |
| --user | No | string | root | The username for running the test. |
| --password | No | string | Empty | The password for running the test. |
| -t/--tenant | No | string | test | The tenant name used to perform the test. You need ensure this tenant has been created. |
| --database | No | string | test | The database for performing the test. |
| --obclient-bin | No | string | obclient | The path of the OBClient binary file. |
| --sysbench-bin | No | string | sysbench | The path of the Sysbench binary file. |
| --script-name | No | string | point_select.lua | The name of the Sysbench script to be run. |
| --sysbench-script-dir | No | string | /usr/sysbench/share/sysbench | The directory that stores the Sysbench script. |
| --tables | No | int | 30 | The number of tables to be initialized. |
| --table-size | No | int | 20000 | The data size of each table to be initialized. |
| --threads | No | int | 16 | The number of threads to be started. |
| --time | No | int | 60 | Test execution time in seconds. When this option is set to 0, the running duration is not limited. |
| --interval | No | int | 10 | The logging interval, in seconds. Disables intermediate reports When this option is set to 0. |
| --mysql-ignore-errors | No | String | 1062 | The error code to be ignored. Separate multiple error codes with commas (,). The value all indicates to ignore all errors. |
| --events | No | int | 0 | The maximum number of requests. If this option is specified, the --time option is not needed. |
| --rand-type | No | string | Empty | The random number generation function used for data access. Valid values: special, uniform, gaussian, and pareto. Default value: special, early value: uniform. |
| ---skip-trx | No | string | Empty | Specifies whether to enable or disable a transaction in a read-only test. |
| --percentile | No | int | Empty | Percentile to calculate in latency statistics. Value range: [1,100]. 0 means to disable percentile calculations. |
| -S/--skip-cluster-status-check | No | bool | false | Skip cluster status check when the option is true. |
| -O/--optimization | No | int | 1 | The degree of auto-tuning. Valid values: 0, 1, and 2. 0 indicates that auto-tuning is disabled. 1 indicates that the auto-tuning parameters that take effect without a cluster restart are modified. 2 indicates that all auto-tuning parameters are modified. If necessary, the cluster is restarted to make all parameters take effect. |
This section describes how to run the TPC-H test on the specified node of an OcecanBase cluster or ODP. To run the TPC-H test, you must install OBClient and obtpch.
TPC-H needs to specify an OceanBase target server as the execution target. Before executing the TPC-H test, OBD will transfer the data files required for the test to the specified directory of the specified machine. Please make sure that you have enough disk space on this machine because these files may be relatively large.
Of course, you can prepare the data files on the target machine in advance and then turn off the transfer by using the -dt/--disable-transfer option.
obd test tpch <deploy name> [flags]
# example
sudo yum install obtpch
obd test tpch test --tenant=tpch -s 100 --remote-tbl-dir=/tmp/tpch100The deploy name parameter specifies the name of the deployed cluster. You can consider it as an alias for the configuration file.
| Option | Required | Data type | Default value | Description |
|---|---|---|---|---|
| --component | No | string | Empty | The name of the component to be tested. Valid values: oceanbase-ce, oceanbase, obproxy-ce and obproxy. If you do not specify a value, the existence of obproxy, obproxy-ce, oceanbase, oceanbase-ce is checked sequentially. The traversal stops when a component is found, and the component is then tested. |
| --test-server | No | string | The first node of the specified component. | Machine to be tested, followed by the name value corresponding to servers in the yaml file. If the name value is not configured after servers, the ip value is used. It must be the name of a node of the specified component. |
| --user | No | string | root | The username for running the test. |
| --password | No | string | Empty | The password for running the test. |
| -t/--tenant | No | string | test | The tenant name used to perform the test. You need ensure this tenant has been created. |
| --database | No | string | test | The database for performing the test. |
| --obclient-bin | No | string | obclient | The path of the OBClient binary file. |
| --dbgen-bin | No | string | /usr/tpc-h-tools/tpc-h-tools/bin/dbgen | The path of the dbgen binary file. |
| --dss-config | No | string | /usr/tpc-h-tools/tpc-h-tools/ | The directory that stores the dists.dss files. |
| -s/--scale-factor | No | int | 1 | Automatically generate the scale of test data, the data is measured in Gigabytes. |
| --tmp-dir | No | string | ./tmp | Temporary directory when executing tpch. When enabled, this option will automatically generate test data, auto-tuned SQL files, log files for executing test SQL, and so on. |
| --ddl-path | No | string | Empty | The path or directory of the ddl file. If it is empty, OBD will use the ddl file that comes with it. |
| --tbl-path | No | string | Empty | The path or directory of the tbl file. If it is empty, use dbgen to generate test data. |
| --sql-path | No | string | Empty | The path or directory of the sql file. If it is empty, OBD will use the sql file that comes with it. |
| --remote-tbl-dir | No | string | Empty | The directory where the tbl is stored on the target observer, it is the absolute path. Please make sure that you have the read and write permissions to this directory when you start the server. This option is required when --test-only is not enabled. |
| --test-only | No | bool | false | When you enable this option, initialization will not be done, only the test SQL is exectued. |
| --dt/--disable-transfer | No | bool | false | Disable transfer. When you enable this option, OBD will not transfer the local tbl to the remote remote-tbl-dir, and OBD will directly use the tbl file under the target machine remote-tbl-dir. |
| -S/--skip-cluster-status-check | No | bool | false | Skip cluster status check when the option is true. |
| -O/--optimization | No | int | 1 | The degree of auto-tuning. Valid values: 0, 1, and 2. 0 indicates that auto-tuning is disabled. 1 indicates that the auto-tuning parameters that take effect without a cluster restart are modified. 2 indicates that all auto-tuning parameters are modified. If necessary, the cluster is restarted to make all parameters take effect. |
You can run this command to perform a TPC-C test on a specified node of an OceanBase cluster or an OceanBase Database Proxy (ODP) component.
Make sure that you have installed OBClient and obtpcc, which are required to perform a TPC-C test.
obd test tpcc <deploy name> [flags]
# example
sudo yum install obtpcc java
obd test tpcc test --tenant=tpcc --warehouses 10 --run-mins 1The deploy name parameter specifies the name of the deployed cluster. You can consider it as an alias for the configuration file.
The following table describes details about the available options.
| Option | Required | Data type | Default value | Description |
|---|---|---|---|---|
| --component | No | string | Empty | The name of the component to be tested. Valid values: oceanbase-ce, oceanbase, obproxy-ce and obproxy. If you do not specify a value, the existence of obproxy, obproxy-ce, oceanbase, oceanbase-ce is checked sequentially. The traversal stops when a component is found, and the component is then tested. |
| --test-server | No | string | The name of the first node under the specified component. | Machine to be tested, followed by the name value corresponding to servers in the yaml file. If the name value is not configured after servers, the ip value is used. The name of the node to be tested under the specified component. |
| --user | No | string | root | The username used to perform the test. |
| --password | No | string | Empty | The user password used to perform the test. |
| -t/--tenant | No | string | test | The tenant name used to perform the test. You need ensure this tenant has been created. |
| --database | No | string | test | The database where the test is to be performed. |
| --obclient-bin | No | string | obclient | The path to the directory where the binary files of OBClient are stored. |
| --java-bin | No | string | java | The path to the directory where the Java binary files are stored. |
| --tmp-dir | No | string | ./tmp | The temporary directory to be used for the TPC-C test. Automatically generated configuration files, auto-tuned SQL files, and test output files will be stored in this directory. |
| --bmsql-dir | No | string | Empty | The installation directory of BenchmarkSQL. You need to specify this option only if you manually compile and install BenchmarkSQL. If you use obtpcc, this option is not required. |
| --bmsql-jar | No | string | Empty | The path to the directory where the JAR file of BenchmarkSQL is stored. If you do not specify the path, and the BenchmarkSQL directory is not specified, the default installation directory generated by obtpcc is used. If the BenchmarkSQL directory is specified, the JAR file in the <bmsql-dir>/dist directory is used. |
| --bmsql-libs | No | string | Empty | If the BenchmarkSQL directory is specified, the JAR files in the <bmsql-dir>/lib and <bmsql-dir>/lib/oceanbase directories are used. If you use obtpcc, this option is not required. |
| --bmsql-sql-dir | No | string | Empty | The path to the directory where the SQL files for the TPC-C test are stored. If you do not specify the path, OceanBase Deployer (OBD) uses the SQL files that are automatically generated. |
| --warehouses | No | int | 10 | The number of warehouses for the TPC-C test data set. If you do not specify a value, the assigned value is 20 times the number of CPU cores allocated to the OceanBase cluster. |
| --load-workers | No | int | Empty | The number of concurrent worker threads for building the test data set. If you do not specify a value, the number of CPU cores per server or the size of tenant memory (GB)/2, whichever is smaller, is used. |
| --terminals | No | int | Empty | The number of virtual terminals to be used for the TPC-C test. If you do not specify a value, the number of CPU cores for the OceanBase cluster × 15 or the number of warehouses × 10, whichever is smaller, is used. |
| --run-mins | No | int | 10 | The amount of time allocated for the execution of the TPC-C test. |
| --test-only | No | bool | false | Specifies that the test is performed without data construction. |
| -S/--skip-cluster-status-check | No | bool | false | Skip cluster status check when the option is true. |
| -O/--optimization | No | int | 1 | The degree of auto-tuning. Valid values: 0, 1, and 2. 0 indicates that auto-tuning is disabled. 1 indicates that the auto-tuning parameters that take effect without a cluster restart are modified. 2 indicates that all auto-tuning parameters are modified. If necessary, the cluster is restarted to make all parameters take effect. |