Closed SosthenG closed 5 months ago
Please check and adjust the timeout in the plugin settings (navigate to Settings | Tools | Elasticsearch | Connection Timeout). After the recent update, the timeout now applies to both connection establishment and requests. I'll increase the default value and probably split the request and connection timeouts in a future update.
Oh sorry my mistake, I didn't know that was already there I was looking in the cluster configuration. Thank you!
Describe the bug I'm getting a lot of "Error: Read timed out" when trying to perform some requests that runs fine in any other way.
Steps to reproduce I don't know what exactly is going wrong, all my requests does not fail but some do most of the times, not always. Looks like there is a low timeout on the requests made by the plugin?
Expected behavior Get a result, or be allowed to configure the timeout if it's needed by the plugin.
Environment information: