-
Notifications
You must be signed in to change notification settings - Fork 34
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
Local ClickHouse cluster configuration #33
Conversation
docker-compose.cluster.yml
Outdated
- '9000:9000' | ||
- '9181:9181' | ||
volumes: | ||
- './.docker/clickhouse/cluster/config1.xml:/etc/clickhouse-server/config.xml' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional: what if we give them more descriptive names? config1.xml
--> server_1_config.xml
?
Going forward I would suggest creating a separate module for reusing that in other drivers/clients (the cluster creation part) |
@mzitnik that's a good idea, will do in a new PR |
query, | ||
...this.getBaseParams(params), | ||
}); | ||
|
||
return new Rows(stream, format); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thinking loudly: we need to rename the result of the operation. not a blocker for the current PR
case 'CLOUD': | ||
env = TestEnv.Cloud; | ||
break; | ||
case 'LOCAL_CLUSTER': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do we set it? Shouldn't we add a command to package.json
to run the tests against a local cluster? Can be done in follow-up, though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently in GHA only:
CLICKHOUSE_TEST_ENVIRONMENT: 'cloud' |
but I agree
On top of #22, to keep it cleaner for the review.
Now we can run a ClickHouse cluster locally, with 2 nodes and Clickhouse Keeper (no Zookeeper)
Nginx serves as a load balancer to expose a single ClickHouse endpoint like it is done in the Cloud.