You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we are running CH v. 18.14.9 and have a typical table setup: Distributed table -> ReplicatedMergeTree (3 different dbs / replicas / disks per node)
Tables have a column col1 LowCardinality(UInt64).
When running query:
SELECT distinct(col1) FROM distributed
Rows start pouring in the client window (there are exactly 132 distinct values in the whole table, it seems distinct doesn't apply and many more rows are returned). Then the query fails with exception:
Received exception from server (version 18.14.9):
Code: 32. DB::Exception: Received from node2:9001, xx.xx.xx.xx. DB::Exception: Attempt to read after eof: while receiving packet from node03:9001, xx.xx.xx.xx.
Moreover, random number of CH nodes (I observed 1 to 6) in the cluster fail with:
If I query local replicated table everything is fine and results are correct. If I add toString(...) around the column, everything works also on the distributed table.
Sorry for not providing a complete test case to reproduce, no time to spare.
The text was updated successfully, but these errors were encountered:
Hey guys,
we are running CH v.
18.14.9
and have a typical table setup:Distributed
table ->ReplicatedMergeTree
(3 different dbs / replicas / disks per node)Tables have a column
col1 LowCardinality(UInt64)
.When running query:
Rows start pouring in the client window (there are exactly
132
distinct values in the whole table, it seemsdistinct
doesn't apply and many more rows are returned). Then the query fails with exception:Moreover, random number of CH nodes (I observed 1 to 6) in the cluster fail with:
If I query local replicated table everything is fine and results are correct. If I add
toString(...)
around the column, everything works also on the distributed table.Sorry for not providing a complete test case to reproduce, no time to spare.
The text was updated successfully, but these errors were encountered: