09.08.2018 · It looks like the data for INSERT queries was not sent for more than 300 seconds. (Probably there was some data, then a pause for more than 300 seconds.) You should consult with author of the library: @kshvakov. Also you can increase timeouts: it is send_timeout and receive_timeout.
29.09.2020 · "3 node cluster with 2 clickhouse instances" - a little confusing sentence, are you using circular cluster topology (where one node hosts two replicas)? – vladimir Sep 29 '20 at …
29.03.2020 · after that when I run command clickhouse-client it shows something like this : root@busmap-api-test:~# clickhouse-client ClickHouse client version 20.3.5.21 (official build) Connecting to localhost:9000 as user default. Code: 209. DB::NetException: Timeout exceeded while reading from socket (127.0.0.1:9000)
28.03.2019 · ClickHouse server version 19.4.1.1. Whenever set receive_timeout is used (e.g. set receive_timeout=6000), the change is reflected in system.settings:
client_name – this name will appear in server logs. Defaults to 'python-driver'. connect_timeout – timeout for establishing connection. Defaults to 10 seconds. send_receive_timeout – timeout for sending and receiving data. Defaults to 300 seconds. sync_request_timeout – timeout for server ping. Defaults to 5 seconds.
connect_timeout – timeout for establishing connection. Defaults to 10 seconds. send_receive_timeout – timeout for sending and receiving data. Defaults to 300 ...
If the timeout has passed and no write has taken place yet, ClickHouse will generate an exception and the client must repeat the query to write the same block to the same or any other replica. Default value: 600 000 milliseconds (ten minutes).