tctl v1.17 admin command reference
The tctl command line utility has been deprecated and is no longer actively supported. We recommend transitioning to Temporal CLI for continued use and access to new features.
Thank you for being a valued part of the Temporal community.
A tctl admin
command allows the user to run admin operations.
Modifiers:
--help
tctl admin [--help | -h]
cluster
The tctl admin cluster
command runs the administrator-level operations on a given Cluster.
tctl admin cluster command [command modifiers] [arguments...]
- add_search_attributes
- remove_search_attributes
- get_search_attributes
- describe
- list
- upsert_remote_cluster
- remove_remote_cluster
add_search_attributes
The tctl admin cluster add-search-attributes
command allows Search Attributes to be added to a Cluster.
Custom Search Attributes can be used to make a Cluster more identifiable.
Due to Elasticsearch limitations, you can only add new custom Search Attributes. Existing Search Attributes cannot be renamed or removed from the Elasticsearch index.
Use this command to add custom Search Attributes to your Temporal Cluster:
tctl admin cluster add-search-attributes --name <SearchAttributeName> --type <SearchAttributeValueType>
If you are adding custom Search Attributes to a Cluster running from the docker-compose-es.yml
file in the temporalio/docker-compose repo, make sure to increase the Docker memory to more than 6 GB.
--skip_schema_update
Allows the user to skip the Elasticsearch index schema update.
This will only register in metadata.
--name
The name of the Search Attribute to add. Names can have multiple values.
Search Attribute names are case sensitive.
--type
The type of Search Attribute to add. Multiple values can be added at once.
Values: Text, Keyword, Int, Double, Bool, Datetime
describe
The tctl admin cluster describe
command provides information for the current Cluster.
The following modifier changes the behavior of the command:
--cluster_value
The name of the remote Cluster within the current Cluster.
This modifier is optional, and can default to the return of current Cluster information.
get_search_attributes
The tctl admin cluster get_search_attributes
command retrieves existing Search Attributes for a given Cluster.
The following modifier will change the behavior of the command:
--print_json
Prints the existing search attributes in JSON format.
list
The tctl admin cluster list
command lists Cluster information on the given Cluster.
Default: 100
The modifier below changes the behavior of the command:
--pagesize
The size of the page that the list is printed on.
remove_remote_cluster
The tctl admin cluster remove_remote_cluster
command removes remote Cluster information on the given Cluster.
The modifier below changes the behavior of the operation:
--cluster
The name of the remote Cluster to remove.
remove_search_attributes
The Temporal tctl documentation covers version 1.17 of the Temporal CLI.
The tctl admin cluster remove-search-attributes
command removes custom Search Attribute metadata from a Cluster.
This operation has no effect on Elasticsearch index schema.
Use the following command to remove a Search Attribute from a Cluster's metadata:
tctl admin cluster remove-search-attributes --name <SearchAttributeKey>
Only custom Search Attributes can be removed from a Cluster's metadata. Default Search Attributes cannot be removed.
Removing a Search Attribute removes it from the Cluster's metadata but does not remove it from the Elasticsearch index. This means that the Search Attribute can be added back later as the same type. After a Search Attribute has been added to the Elasticsearch index, it cannot be changed.
The following modifier changes the behavior of the operation:
--name
Name of the Search Attribute to remove.
upsert_remote_cluster
The tctl admin cluster upsert_remote_cluster
command adds or updates remote Cluster information in the current Cluster.
--frontend_address
The remote Cluster frontend address.
--enable_connection
Enables remote Cluster connection.
db
The tctl admin db
command runs administrator-level operations on a given database.
Usage
tctl admin db command [command modifiers] [arguments...]
Commands
clean
The tctl admin db clean
command cleans corrupted Workflow Executions from the targeted database.
The modifiers below change the behavior of the command.
--db_engine
Type of DB engine to use
Default: cassandra
Value: cassandra
| mysql
| postgres
--db_address
Persistence address for the database.
Default: 127.0.0.1
--db_port
Persistence port for the DB.
Default: 9042
--username
Database username.
--password
Database password.
--keyspace
Database keyspace
Default: "temporal"
--input_directory
The directory which contains the corrupted Workflow Execution files from running scan
.
--lower_shard_bound
The minimum amount (inclusive) of corrupt shards to handle.
Default: 0
--upper_shard_bound
The maximum amount (exclusive) of corrupt shards to handle.
Default: 16384
--starting_rps
starting rps of database queries.
Default: 100
--rps
Target rps of database queries.
Default: 7000
--concurrency
Number of threads to handle a scan.
Default: 1000
--report_rate
The number of shards handled between each emittance of progress.
Default: 10
Enable --tls
before using any of the following modifiers.
--tls_cert_path
Where the tls client cert is located.
--tls_key_path
Where the tls key is located.
--tls_ca_pat
Where the tls ca is located.
--tls_server_name
The name of the Db tls server.
--tls_disable_host_verification
Disables verification of the DB tls hostname and server cert.
scan
The tctl admin db scan
command scans concrete Workflow Executions in a given database, and detects corrupted ones.
--db_engine
Type of DB engine to use
Default: cassandra
Value: cassandra
| mysql
| postgres
--db_address
Persistence address for the DB.
Default: 127.0.0.1
--db_port
Persistence port for the DB.
Default: 9042
--username
DB username.
--password
DB password.
--keyspace
DB keyspace
Default: "temporal"
--lower_shard_bound value
The minimum amount (inclusive) of corrupt shards to handle.
Default: 0
--upper_shard_bound
The maximum amount (exclusive) of corrupt shards to handle.
Default: 16384
--starting_rps
starting rps of database queries.
Default: 100
--rps value
Target rps of database queries.
Default: 7000
--pagesize
The size of the page used to query database executions.
Default: 500
--concurrency
Number of threads to handle a scan.
Default: 1000
--report_rate
The number of shards handled between each emittance of progress.
Default: 10