ClickHouse Without Pain: Our Experience Refactoring a Legacy Cluster and the Impact of Shard Groups
summary
Practical lessons from refactoring a legacy ClickHouse cluster: common mistakes in building and operating ClickHouse, the negative consequences observed, and concrete ways to avoid them. Also covers rolling out shard groups (shard_group feature) and the operational effects seen after that change.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:09Data warehouse architecture
- 2:57ClickHouse implementation errors
- 6:32Reasons for new ClickHouse
- 7:34Post-migration solutions
- 8:37Refactoring problems
- 9:17Shard groups in ClickHouse
- 13:11Distributed table behavior
- 14:15Gradual shard-group transition
- 15:44Refactoring results
- 16:48Monitoring and metrics
- 18:58Data volumes and load
- 20:01Q&A
- 41:30Fault tolerance and replication
- 43:39Bad query monitoring
- 45:05Cloud and infrastructure cost
related talks
59mEffective Use of ClickHouse
51mWhat You Need to Know About ClickHouse Architecture
53mClickHouse Is Slowing Down
53mClickHouse capabilities for advanced developers
42mOptimizing ClickHouse query performance
53mClickHouse: blitz meetup (questions and answers)
51mHow to Survive a One-Year Sprint and Migrate to ClickHouse
49mFlagrant Bugs and How to Avoid Them: The ClickHouse Example
