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

Use longer socket timeout elastic index command

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 10.10-HF55, 2021.12
    • Component/s: Elasticsearch
    • Release Notes Summary:
      A longer socket timeout is used by elastic index commands.
    • Upgrade notes:
      Hide

      Since 10.10-HF55 elasticsearch max retry timeout is configurable with elasticsearch.restClient.maxRetryTimeoutMs and set to 60s, this option is specific to Nuxeo 10.10/Elastic 6.x and doesn't exist on 2021 LTS.

      Show
      Since 10.10-HF55 elasticsearch max retry timeout is configurable with elasticsearch.restClient.maxRetryTimeoutMs and set to 60s, this option is specific to Nuxeo 10.10/Elastic 6.x and doesn't exist on 2021 LTS.
    • Team:
      PLATFORM
    • Sprint:
      nxplatform #48, nxplatform #49
    • Story Points:
      1

      Description

      Like in NXP-30470 the index command should use a 2min socket timeout instead of 30s.

      Also, in 10.10 we want to avoid reaching the maxRetryTimeout that can produce a listener timeout after 30s by default,
      this can be done by providing an option to configure this specific timeout.
      In LTS this is not necessary because the maxRetryTimeout option has been removed in elastic 7.x.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: