Skip to content

DDLWorker Fails for ON CLUSTER Statements in Multiple ClickHouse Versions (Including 25.10.2.65 and 25.11.1) #1883

@EinavDanielDX

Description

@EinavDanielDX

DDLWorker Fails for ON CLUSTER Statements Across Multiple ClickHouse Versions (Including 25.10.2.65 and 25.11.1)

Summary

We are encountering consistent DDLWorker failures when executing any ON CLUSTER DDL statements across multiple ClickHouse versions, all under the Altinity Operator v0.24.4.

The issue is not limited to ClickHouse v25.8.10.7-lts (as described in upstream ClickHouse issue #89693) and also occurs in:

  • ClickHouse 25.10.2.65
  • ClickHouse 25.11.1

This suggests a broader regression or compatibility issue affecting distributed DDL execution under operator-managed clusters.

Upstream reference:
ClickHouse/ClickHouse#89693


Problem Description

Executing any DDL statement using ON CLUSTER consistently fails in DDLWorker. For example:

CREATE TABLE ... ON CLUSTER '{cluster}';

Errors observed:

Code: 999. DDLWorker failed to execute query ...

This prevents schema propagation and blocks automated migrations in multi-shard/multi-replica environments.

Additional Notes

  • The issue occurs consistently across several ClickHouse versions, not just the one affected upstream.
  • Possibly related to upstream issue #89693, but reproducible even on newer releases.
  • Requesting guidance on:
    -- Whether the operator requires patches/workarounds,
    -- Whether certain ClickHouse versions should be considered incompatible,
    -- Or if the operator should enforce version restrictions until resolved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions