stasDomb

Thanks a lot for your answer. You are right. When I tried with 1.6 version I could connect. And everything is OK. And could you help me with the freshest...

Thank you. guys. I see... I have tried already and I couldn't because of some errors. I will try another time or maybe I will continue to use the 1.6...

I'm sorry. Could you please help me? I'm trying to use the example: clickhouse-keeper-3-nodes.yaml And I got the keeper deployment but it doesn't connect to ClickHouse. I think, I have...

The problem was fixed when I just put service name as a host: ``` nodes: - host: clickhouse-keeper port: 2181 ```

The same problem. Superset versions: 2.0.0, 2.0.1, 1.5.1,1.5.2. And for me it's unstable. At some point it starts working good...

Could somebody help with that? Checked with helm chart 0.7.6 and 2.0.1rc2. Still have this problem.

I've resolved this issue with removing all deployments and re-deploy after that. Looks like when you migrate from one version to another sometimes there are some problems with DB initialisation

> Hi @stasDomb, thanks for reporting the issue. Is there any clue on server side? Are you using proxy between the client and server? Hello, thank you for the answer....

Hello, after updating to the version 5.0.0 the previous error was vanished, but a new one was appeared: `java.sql.BatchUpdateException: The target server failed to respond, server ClickHouseNode [uri=http://hostname:8123/default]@1702260979 at com.clickhouse.jdbc.SqlExceptionUtils.batchUpdateError(SqlExceptionUtils.java:107)...

> Hello! Do you have any updates on this issue? I faced with the similar exception: > > ``` > Caused by: java.sql.BatchUpdateException: The target server failed to respond, server...