Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- cs-availability

Assigned Teams:

Cluster Scalability
Backport Requested:

v8.1, v8.0
Linked BF Score:
200
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The meaning of this error was modified slightly as a result of refactoring in the network interface code. It is now considered a general timeout error, and the sharding code should not always make the server unavailable if this error occurs.

depends on

SERVER-79888 find/getMore timeouts triggered by Fetcher always reported as NetworkInterfaceExceededTimeLimit

Backlog

SERVER-80020 The exhaustiveFindOnConfig() method should retry on NetworkInterfaceExceededTimeLimit errors

Backlog

SERVER-81877 Use MaxTimeMsExpired in ShardRemote::_scheduleCommand if pass maxTimeMs for timeout

Closed

is related to

SERVER-72055 NetworkInterfaceTL should by default return a retryable error when it times out waiting to acquire a connection

Closed

SERVER-109023 Require specification of timeoutCode when timeout is specified in RemoteCommandRequest

Blocked

Assignee:: Unassigned
Reporter:: Lamont Nelson
Participants:: Lamont Nelson
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: May 17 2024 07:59:49 PM UTC
Updated:: Aug 08 2025 05:02:28 PM UTC
Confidence Status Last Update:: 22/May/24 8:37 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates