Skip to main content
These settings are available in system.settings and are autogenerated from source.

distributed_ddl_entry_format_version

Compatibility version of distributed DDL (ON CLUSTER) queries Cloud default value: 6.

distributed_ddl_output_mode

Sets format of distributed DDL query result. Possible values:
  • throw — Returns result set with query execution status for all hosts where query is finished. If query has failed on some hosts, then it will rethrow the first exception. If query is not finished yet on some hosts and distributed_ddl_task_timeout exceeded, then it throws TIMEOUT_EXCEEDED exception.
  • none — Is similar to throw, but distributed DDL query returns no result set.
  • null_status_on_timeout — Returns NULL as execution status in some rows of result set instead of throwing TIMEOUT_EXCEEDED if query is not finished on the corresponding hosts.
  • never_throw — Do not throw TIMEOUT_EXCEEDED and do not rethrow exceptions if query has failed on some hosts.
  • none_only_active - similar to none, but doesn’t wait for inactive replicas of the Replicated database. Note: with this mode it’s impossible to figure out that the query was not executed on some replica and will be executed in background.
  • null_status_on_timeout_only_active — similar to null_status_on_timeout, but doesn’t wait for inactive replicas of the Replicated database
  • throw_only_active — similar to throw, but doesn’t wait for inactive replicas of the Replicated database
Cloud default value: none_only_active.

distributed_ddl_task_timeout

Sets timeout for DDL query responses from all hosts in cluster. If a DDL request has not been performed on all hosts, a response will contain a timeout error and a request will be executed in an async mode. Negative value means infinite. Possible values:
  • Positive integer.
  • 0 — Async mode.
  • Negative integer — infinite timeout.
Last modified on July 23, 2026