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

How to set JDBC connection string for Clickhouse cluster #423

Closed
gubinjie opened this issue Feb 12, 2020 · 4 comments · Fixed by #956
Closed

How to set JDBC connection string for Clickhouse cluster #423

gubinjie opened this issue Feb 12, 2020 · 4 comments · Fixed by #956

Comments

@gubinjie
Copy link

I set up a ClickHouse cluster with 3 partitions and 1 replica, but when I use a JDBC connection, I can only choose one of the IP addresses to use as the connection string, which has a single point of failure. I try to use nginx (ip: 30.23.78.112) as the listening port 8123 and forward the request to the Clickhouse host, so is the JDBC connection string (jdbc: clickhouse: //30.23.78.112: 8123 / database name) I use correct?

@4ertus2
Copy link

4ertus2 commented Feb 12, 2020

FYI, @alex-krash
I think it's an issue for https://github.com/ClickHouse/clickhouse-jdbc

@den-crane
Copy link
Collaborator

@blinkov blinkov transferred this issue from ClickHouse/ClickHouse Feb 13, 2020
@todd5167
Copy link

todd5167 commented Mar 2, 2020

@den-crane use BalancedClickhouseDataSource,need to use API to manipulate data, inconvenient

@den-crane
Copy link
Collaborator

@todd5167 That's OK. You can use another JDBC driver if you don't like this one.

@zhicwu zhicwu added this to the 0.3.3 release milestone Dec 29, 2021
@zhicwu zhicwu modified the milestones: 0.3.3 release, 0.3.2-patch10 May 31, 2022
@zhicwu zhicwu linked a pull request Jun 20, 2022 that will close this issue
@zhicwu zhicwu closed this as completed Jun 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants