Open bessonov87 opened 6 months ago
While we were waiting for some kind of answer here, we decided to try to do something ourselves. As a result, we were helped by recreating the tables with a new syntax. We accidentally noticed that the errors were related to parts of tables created using the old syntax. We have databases that were created more than 6 years ago and there are quite a lot of old tables in there. So after recreating tables with changing old syntax like this
ENGINE = ReplicatedMergeTree('/clickhouse/tables/{shard}/migration_clickhouse', '{replica}', eventDate, (version, apply_time), 8192)
to the current one like this
ENGINE = ReplicatedMergeTree('/clickhouse/tables/{shard}/migration_clickhouse', '{replica}')
PARTITION BY toYYYYMM(eventDate)
ORDER BY (version, apply_time)
SETTINGS index_granularity = 8192
errors disappear and backups begin to be created.
I'm not sure if this is a bug or not, but at least it's unexpected behavior.
ClickHouse versions: 23.8 and 24.3.
I tried to start a backup using the following query:
Here is the result:
We have several clusters and I have tested backups on 3 of them. Everything is working fine on one of them but doesn't work on the other two backups failed with the same error described above. All of them had version 23.8
What can be the reason for such behavior and what can be done to fix this issue?
Here is the information about that part in case is needed: