This page introduces the
cockroach commands for configuring, starting, and managing a CockroachDB cluster, as well as logging flags that can be set on any command and environment variables that can be used in place of certain flags.
You can run
cockroach help in your shell to get similar guidance.
||Start a node.|
||Create CA, node, and client certificates.|
||Drain and shutdown a node.|
||Use the built-in SQL client.|
||Get, set, list, and remove users.|
||Configure the number and location of replicas for specific sets of data.|
||List node IDs and show their status.|
||Back up a table by outputting the SQL statements required to recreate the table and all its rows.|
||Generate manpages, a bash completion file, and example data.|
||Output CockroachDB version and dependency details.|
cockroach start logs all messages to files, and client commands log messages to
||Copy log messages at or above this severity level to
||Write log files in this directory. Log files are named as follows:
Default: For the
||Write log messages of all severities to
||Do not colorize
--vmodule flags are intended for internal debugging.
For many common
cockroach flags, such as
--user, you can set environment variables once instead of manually passing the flags each time you execute commands.
- To find out which flags support environment variables, see the documentation for each command.
- To output the current configuration of CockroachDB and other environment variables, run
- When a node uses environment variables on startup, the variable names are printed to the node’s logs; however, the variable values are not.
CockroachDB prioritizes command flags, environment variables, and defaults as follows:
- If a flag is set for a command, CockroachDB uses it.
- If a flag is not set for a command, CockroachDB uses the corresponding environment variable.
- If neither the flag nor environment variable is set, CockroachDB uses the default for the flag.
- If there’s no flag default, CockroachDB gives an error.