-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
Fully Compatible
-
ALL
-
ClusterScalability Mar31-Apr14
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The reshardingChangeStreamsMonitor calls killCursors on active cursors during cleanup. If a cursor is in the process of running an operation, the killCursor command will kill the operation and the cursor will stop on its own and subsequently get destroyed(code link). This is expected behavior for the cursor_manager and the unit test should not consider cursors marked as "killPending": true as open cursors in this check here.