-
Notifications
You must be signed in to change notification settings - Fork 52
Closed
Description
I have a multi-threaded program that is writing 100k write with 10K batches and at the same time reading values from the same table. I see this error and I have tried a few options however not been successful.
Thread 0: inserting 100000 random rows
Thread 3: inserting 100000 random rows
Thread 1: inserting 100000 random rows
Thread 2: inserting 100000 random rows
Thread 4: inserting 100000 random rows
Thread 5: inserting 100000 random rows
Thread 6: inserting 100000 random rows
Thread 7: inserting 100000 random rows
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
Exception: influx-cxx [treatCurlResponse]: Timeout was reached
terminate called after throwing an instance of 'influxdb::ConnectionError'
what(): influx-cxx [treatCurlResponse]: Timeout was reached
I tried and increased the write-timeout for coordinator in the influxdb.conf
[coordinator]
The default time a write request will wait until a "timeout" error is returned to the caller.
write-timeout = "600s"
#max-concurrent-queries = 0
#query-timeout** = "0s"
[http]
#Added these timeouts
read-timeout = "600s"
write-timeout = "600s"
[subscriber]
http-timeout = "1800s"
then I restarted the influxDB. I don't see how to increase the read-timeout and see this is happening. could you please help me on how to increase the timeout from default 10s to something larger? I see that after 10 seconds the timeout is happening.