Timeout was reached

Under heavy load or slow networks the backend is not able to respond before the client times out. I see in the client log Timeout was reached and in the server log a 499 indicating it was still processing the request when the client closed the connection. Ultimately this results in a read error.

Is there a way to configure the drive’s timeout so this can be tailored to the deployment environment?

1 Like