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
I'm facing an issue with recovering data after replica loss. After StatefullSet and PVCs corresponding to a replica are deleted, and then re-created by manually specifying spec.taskID in the ClickHouseInstallation yaml file, the schema isn't restored on the re-created replica.
Description
I'm facing an issue with recovering data after replica loss. After StatefullSet and PVCs corresponding to a replica are deleted, and then re-created by manually specifying
spec.taskID
in theClickHouseInstallation
yaml file, the schema isn't restored on the re-created replica.Setup
Versions
clickhouse-operator
:0.22.2
clickhouse-server
:23.8
clickhouse-keeper
:23.8-alpine
Steps to reproduce
chi.yaml
Pods after deployment is :
schema.sql
SYSTEM DROP REPLICA 'chi-recovery-test-ch-ha-0-0'
spec.taskID
inClickHouseInstallation
yaml file to some random string and apply it, forcing reconciliationchi-recovery-test-ch-ha-0-0
replica to be re-createdtest_db
andtest_table_local
are present onchi-recovery-test-ch-ha-0-0
replicaExpected result
test_db
andtest_table_local
are present onchi-recovery-test-ch-ha-0-0
replica, data intest_table_local
is recovered from the live replica.Actual result
Schema is not recreated, data isn't recovered
I've also observed these messages in the operator log:
It seems like instead of
chi-recovery-test-ch-ha-0-0
, operator tried to create schema onchi-recovery-test-ch-ha-0-1
?....Here is the full log:
Operator log
The text was updated successfully, but these errors were encountered: