-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
Fully Compatible
-
ALL
-
200
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When mongos receives a response from a remote shard with non-ok Status, it kills the cursor because, in case of an error, it cannot guarantee that data have not been corrupted. After SERVER-102476, if a remote cursor is not found the status of the response is not OK anymore but CursorNotFound. So, mongos kills the cursor. This is not correct and this error should be ignored since it indicates that the data were not processed.
- is related to
-
SERVER-102476 Refactor releaseMemory command to use ARM
-
- Closed
-