ClickHouse Cluster Playground
A multi-node cluster for exploring scaling capabilities of ClickHouse.
💡 For use cases that don't require ClickHouse's scaling capabilities, you can use this single-node playground.
🔧 System Components
- ClickHouse Server: High-performance columnar database engine optimized for analytics
- ClickHouse Keeper: Distributed coordination service for cluster management
🛠️ Tools
clickhouse-client: Interactive command-line client for running queriesclickhouse-local: Tool for processing local files with ClickHouse SQL
🎯 Getting Started
Connecting to the Cluster
# Connect to any node in the cluster
clickhouse-client
# Connect with specific database
clickhouse-client --database=default
# Execute single query
clickhouse-client --query "SELECT version()"
# Check cluster configuration
clickhouse-client --query "SELECT * FROM system.clusters"
Credentials
If you need to connect from another client, use the following credentials:
- Host:
localhost(any cluster node) - Port:
9000(native) or8123(HTTP) - Username:
default - Password:
iximiuz - Database:
default
📚 Learn More
🧩 Related Content
🧪 Playgrounds
Happy clustering! 🚀
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs →
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs →
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs →
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs →
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs →
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs →
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs →
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs →
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs →