Altinity / Altinity/clickhouse-operator
Re-Creating node from scratch does not copy tables for the Postgres and Kafka engines
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
We use your Operator to manage Clickhouse cluster. Thank you.
After some hardware failure we reset PVC (and zookeeper namespace) to re-create one clickhouse node.
Most of metadata like views, materialized views and tables with most engines (MergeTree, ReplicatedMergeTree etc.) was successfully re-created on the node and replication was started.
Meantime none of Postgres and Kafka based engines tables was recreated.
Is it a bug, or we need to use some commands or hacks to sync all metadata across the cluster?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ClickHouse Operator's node recreation flow after a PVC and ZooKeeper namespace reset, reproducing the difference between ordinary tables and tables using the Postgres or Kafka engines. Trace how metadata replication is handled for those engines; done means establishing whether the behavior is expected and identifying a documented command, configuration change, or correction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, kafka, kubernetes, postgresql
- Domain
- databases, devops, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100