-
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.
-
Tags:
-
Upgrade notes:
-
Team:PLATFORM
-
Sprint:nxplatform #48, nxplatform #49
-
Story Points:1
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.
- is related to
-
NXP-30470 Use longer Elastic timeout for write operation
-
- Resolved
-
- Is referenced in