To configure the behavior of each Kudu process, you can pass command-line flags when
you start it, or read those options from configuration files by passing them using
one or more --flagfile=<file> options. You can even include the
--flagfile option within your configuration file to include other files. Learn more about gflags
by reading its documentation.

You can place options for masters and tablet servers into the same configuration
file, and each will ignore options that do not apply.

Flags can be prefixed with either one or two - characters. This
documentation standardizes on two: --example_flag.

Only the most common configuration options are documented here. For a more exhaustive
list of configuration options, see the Configuration Reference.

To see all configuration flags for a given executable, run it with the --help option.
Take care when configuring undocumented flags, as not every possible
configuration has been tested, and undocumented options are not guaranteed to be
maintained in future releases.