This article is applicable to the scenario of independent deployment of obdiag. It can be executed with one click to display the lock session information of the cluster on the terminal.
Instructions for use
obdiag display scene run --scene=observer.lockholder [options]
The options are explained below:
Option name |
Is it required |
Data type |
Default value |
Description |
|---|---|---|---|---|
| -c | No | string | ~/.obdiag/config.yml |
Configuration file path. |
| --inner_config | No | string | Default is empty | obdiag's own configuration. |
| --config | No | string | Default is empty | Configuration of the cluster to be diagnosed by obdiag, fixed style: --config key1=value1 --config key2=value2.
ExplanationParameters that support configuration through this option can be found in obdiag configuration. |
| --env | No | string | Default is empty | Additional parameters required by obdiag display, support specifying key=value format multiple times, for example: --env host=127.0.0.1 --env port=2881 --env user=test@test --env password=****** --env database=test. |
| --config_password | No | string | Default is empty | obdiag When using an encrypted configuration file, you need to pass in the corresponding password through this option.
ExplanationFor details, please see Configuration file encryption. |
Usage example
Method 1: Use without configuration file (out of the box)
# Use --env for tenant connection details
obdiag display scene run --scene=observer.lockholder \
--env host=127.0.0.1 --env port=2881 --env user=test@test --env password=****** --env database=test \
--config db_host=xx.xx.xx.xx \
--config db_port=xxxx \
--config tenant_sys.user=root@sys \
--config tenant_sys.password=***
# Without --env, sys tenant is used to list lock-holding sessions for all tenants
obdiag display scene run --scene=observer.lockholder \
--config db_host=xx.xx.xx.xx \
--config db_port=xxxx \
--config tenant_sys.user=root@sys \
--config tenant_sys.password=***
Method 2: Use with configuration file
You need to ensure that the login information of the node to be collected has been configured in the obdiag configuration file config.yml. For related detailed configuration introduction, see obdiag configuration.
# Use --env for tenant connection details
obdiag display scene run --scene=observer.lockholder \
--env host=127.0.0.1 --env port=2881 --env user=test@test --env password=****** --env database=test
# Without --env, sys tenant is used to list lock-holding sessions for all tenants
obdiag display scene run --scene=observer.lockholder