We are seeing requests take more than the default 30s which leads to requests being retried and returning unexpected failures like e.g. "index already exists" because the initial requests that timed out, worked out functionally anyway. => double the timeout to reduce the likelihood of the failures described in #46091 => As suggested in the issue, we should in a follow-up turn off retrying all-together probably
This commit is contained in:
parent
a6cc0deaa0
commit
1bb1c77885
|
@ -834,10 +834,9 @@ public abstract class ESRestTestCase extends ESTestCase {
|
|||
builder.setDefaultHeaders(defaultHeaders);
|
||||
}
|
||||
final String socketTimeoutString = settings.get(CLIENT_SOCKET_TIMEOUT);
|
||||
if (socketTimeoutString != null) {
|
||||
final TimeValue socketTimeout = TimeValue.parseTimeValue(socketTimeoutString, CLIENT_SOCKET_TIMEOUT);
|
||||
builder.setRequestConfigCallback(conf -> conf.setSocketTimeout(Math.toIntExact(socketTimeout.getMillis())));
|
||||
}
|
||||
final TimeValue socketTimeout =
|
||||
TimeValue.parseTimeValue(socketTimeoutString == null ? "60s" : socketTimeoutString, CLIENT_SOCKET_TIMEOUT);
|
||||
builder.setRequestConfigCallback(conf -> conf.setSocketTimeout(Math.toIntExact(socketTimeout.getMillis())));
|
||||
if (settings.hasValue(CLIENT_PATH_PREFIX)) {
|
||||
builder.setPathPrefix(settings.get(CLIENT_PATH_PREFIX));
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue