Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup hot-standby replica for clickhouse cluster #131

Open
hellais opened this issue Dec 19, 2024 · 1 comment
Open

Setup hot-standby replica for clickhouse cluster #131

hellais opened this issue Dec 19, 2024 · 1 comment
Assignees

Comments

@hellais
Copy link
Member

hellais commented Dec 19, 2024

Currently our clickhouse cluster has 3 nodes, 2 data nodes and 3 zookeeper nodes.

Originally we were planning to add a third data node (data2.htz-fsn.prod.ooni.nu), however it's not possible to do that with the current disk setup on the host, since the disks are unevenly sized and a raid5 configuration would lead to too much wasted disk space. We could go for raid0, but that seems a bit risky to do on nvme drives.

In light of this, we should for the moment keep the cluster to be 2 nodes (data3 being the cold replica since it's HDD backed) and discontinue data2 to keep costs down.

For the time being we keep data2.htz-fsn.prod.ooni.nu a reserved hostname label for when we decide to finalize setting it up.

We probably want to do that once we have finished the backend-fsn and backend-hel migration so we can cut down the cost of our dedicated hosts.

@hellais
Copy link
Member Author

hellais commented Dec 19, 2024

I am going to request that data2 is terminated on hetzner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants