Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.11, 6.1.0-rc0
Affects Version/s: None
Component/s: Querying
Labels:
None

Assigned Teams:

Service Arch
Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0, v5.0
Sprint:
Service Arch 2022-04-18, Service Arch 2022-05-02, Service Arch 2022-05-16, Service Arch 2022-05-30, Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11
Linked BF Score:
17

In shard_remote, the maxTimeMS of a query is used as a request timeout. If the time limit is exceeded by the network layer, "NetworkInterfaceExeededTimeLimit" will be returned instead of MaxTimeMSExpired. (e.g. here, here).

is related to

SERVER-63181 Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware

Closed

related to

SERVER-66162 ConnectionPool getConnection may shorten specified connection timeout

Open

SERVER-63181 Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware

Closed

SERVER-65472 Relax time out error code in timeseries_coll_mod.js

Closed

SERVER-67722 Shard cursor is not killed on MaxTimeMSExpired

Closed

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

Investigating

split to

SERVER-66260 Modify executor::RemoteCommand object to accept an option argument

Closed

(1 related to, 1 split to)

Assignee:: [DO NOT USE] Backlog - Service Architecture

Reporter:: Ian Boros

Participants:: [DO NOT USE] Backlog - Service Architecture, Daniel Morilha, David Storch, Githook User, Ian Boros, Lauren Lewis, Max Hirschhorn, Rui Liu, Shane Harvey

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Created:: Sep 04 2019 06:22:07 PM UTC

Updated:: Sep 12 2024 01:01:57 AM UTC

Resolved:: Jul 18 2022 02:39:50 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates