-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 10.10-HF60, 2021.19
-
Component/s: Elasticsearch
-
Release Notes Summary:Default Elastic socket timeout is now set to 2min
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #59
-
Story Points:2
Write requests (like index, delete, refresh and, bulk) have custom 2 minutes timeouts,
but because the elastic client socket timeout is set to 20s (or 1 minute) they have no effect.
Here for instance even if the timeout is set to 2min (that can be seen on the REST endpoint) the 1min socket timeout exception is raised before:
POST /_bulk?timeout=120s HTTP/1.1. Content-Length: 110. Content-Type: application/json. Host: localhost:9200. Connection: Keep-Alive. User-Agent: Apache-HttpAsyncClient/4.1.4 (Java/11.0.14.1). ... org.nuxeo.ecm.core.api.NuxeoException: java.net.SocketTimeoutException: 60,000 milliseconds timeout on connection http-outgoing-0 [ACTIVE] at org.nuxeo.elasticsearch.client.ESRestClient.doBulk(ESRestClient.java:376)
elasticsearch.restClient.socketTimeoutMs should be set to more than 2min by default.
- is related to
-
NXDOC-2541 Update default value for elasticsearch.restClient.socketTimeoutMs
- Resolved