ragsarang
commented
2 years ago Describe the unexpected behaviour When I execute a statement with ON CLUSTER, It should be able to run it on all the shards and replicas. However it is timing out.
How to reproduce
- Which ClickHouse server version to use: 21.12.3.32
- Which interface to use, if matters: Clickhouse-operator
CREATE TABLEstatements for all tables involved:CREATE TABLE events_local on cluster '{cluster}' ( event_date Date, event_type Int32, article_id Int32, title String ) engine=ReplicatedMergeTree('/clickhouse/{installation}/{cluster}/tables/{shard}/{database}/{table}', '{replica}') PARTITION BY toYYYYMM(event_date) ORDER BY (event_type, article_id);
- Queries to run that lead to unexpected result Above one and also create database statement:
CREATE DATABASE test ON CLUSTER '{cluster}' ;Expected behavior The statement should be executed and database/ table should be created successfully
Error message and/or stacktrace
Query id: 98c72107-9eab-40be-b56e-11dcefbf4e59 0 rows in set. Elapsed: 180.672 sec. Received exception from server (version 21.12.3): Code: 159. DB::Exception: Received from localhost:9000. DB::Exception: Watching task /clickhouse/repl-1s1r/task_queue/ddl/query-0000000003 is executing longer than distributed_ddl_task_timeout (=180) seconds. There are 1 unfinished hosts (0 of them are currently active), they are going to execute the query in background. (TIMEOUT_EXCEEDED)Additional context ClickHouse/ClickHouse#33019
I updated clickhouse installation spec with replicasUseFQDN: "yes".
Now the hostname is rendered like below. But the address is not rendered properly and unable to ping the rendered address in hostname section. How can we modify the hostname parameter to render the correct address as per the /etc/hosts ?
SELECT *
FROM system.clusters
Query id: 28ce0733-8f8c-4782-bb66-02495c32d732
┌─cluster──────────────────────────────────────┬─shard_num─┬─shard_weight─┬─replica_num─┬─host_name───────────────────────────────────────────┬─host_address─┬─port─┬─is_local─┬─user────┬─default_database─┬─errors_count─┬─slowdowns_count─┬─estimated_recovery_time─┐
│ all-replicated │ 1 │ 1 │ 1 │ chi-repl-1s1r-replcluster-0-0.ch1.svc.cluster.local │ │ 9000 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ all-sharded │ 1 │ 1 │ 1 │ chi-repl-1s1r-replcluster-0-0.ch1.svc.cluster.local │ │ 9000 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ replcluster │ 1 │ 1 │ 1 │ chi-repl-1s1r-replcluster-0-0.ch1.svc.cluster.local │ │ 9000 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards │ 1 │ 1 │ 1 │ 127.0.0.1 │ 127.0.0.1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards │ 2 │ 1 │ 1 │ 127.0.0.2 │ 127.0.0.2 │ 9000 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards_internal_replication │ 1 │ 1 │ 1 │ 127.0.0.1 │ 127.0.0.1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards_internal_replication │ 2 │ 1 │ 1 │ 127.0.0.2 │ 127.0.0.2 │ 9000 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards_localhost │ 1 │ 1 │ 1 │ localhost │ ::1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_cluster_two_shards_localhost │ 2 │ 1 │ 1 │ localhost │ ::1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_shard_localhost │ 1 │ 1 │ 1 │ localhost │ ::1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_shard_localhost_secure │ 1 │ 1 │ 1 │ localhost │ ::1 │ 9440 │ 0 │ default │ │ 0 │ 0 │ 0 │
│ test_unavailable_shard │ 1 │ 1 │ 1 │ localhost │ ::1 │ 9000 │ 1 │ default │ │ 0 │ 0 │ 0 │
│ test_unavailable_shard │ 2 │ 1 │ 1 │ localhost │ ::1 │ 1 │ 0 │ default │ │ 0 │ 0 │ 0 │
└──────────────────────────────────────────────┴───────────┴──────────────┴─────────────┴─────────────────────────────────────────────────────┴──────────────┴──────┴──────────┴─────────┴──────────────────┴──────────────┴─────────────────┴─────────────────────────┘
13 rows in set. Elapsed: 0.021 sec.
Slach
dabula-s
SolydBoy
Mizoguchee
Describe the unexpected behaviour When I execute a statement with ON CLUSTER, It should be able to run it on all the shards and replicas. However it is timing out.
How to reproduce
CREATE TABLEstatements for all tables involved:CREATE DATABASE test ON CLUSTER '{cluster}' ;Expected behavior The statement should be executed and database/ table should be created successfully
Error message and/or stacktrace
Additional context https://github.com/ClickHouse/ClickHouse/issues/33019