influxdb v1.8.10 SocketTimeOutException:timeout

__Proposal:__
I was doing reading and writing data using influxdb v1.8.10, and I get this ERROR,:
org.influxdb.InfluxDBIOException: java.net.SocketTimeoutException: timeout
sometimes, the error will be read timeout but sometimes it will just show as timeout. I noticed there was a issue that is almost the same as this one, but the solution there is just increase the https timeout time when construct http connection to influxdb. But I am wondering that what actually casuse this error to happen? Is it because too many reading or writting data exceed the influxdb processing limit? But I am handling a situation that the data size is below the limit that is written on the official website of influxdata. if so, is there any disadvantage for increasing http timeout for influxdb, like memroy usage increasing? what http timeout time I should put on? 30s? 60s? 90s?

Start by reproducing the reported reading and writing workload against InfluxDB v1.8.10 and inspect the org.influxdb.InfluxDBIOException and java.net.SocketTimeoutException details. The report does not identify a source file or test; completion would require determining the timeout cause and documenting or implementing a justified resolution, including the appropriate HTTP timeout behavior.

Written by the indexing model from the issue text.