Starting in 9.0.0, this client is configured to not time out any HTTP request by default. Elasticsearch will always eventually respond to any request, even if it takes several minutes. Reissuing a request that it has not responded to yet can cause performance side effects. See theofficial Elasticsearch recommendations for HTTP clients for more information.

Prior to 9.0, this client was configured by default to operate like many HTTP client libraries do, by using a relatively short (30 second) timeout on all requests sent to Elasticsearch, raising aTimeoutError when that time period elapsed without receiving a response.

If you need to set timeouts on Elasticsearch requests, setting therequestTimeout value to a millisecond value will cause this client to operate as it did prior to 9.0.