Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-30957

Elastic socket timeout should be aligned with request timeouts

    Details

    • Release Notes Summary:
      Default Elastic socket timeout is now set to 2min
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #59
    • Story Points:
      2

      Description

      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.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                PagerDuty

                Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.