-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Execution
Currently, this part in shell_helpers.js is not run against sharded cluster since this assertion is expected to fail. On a sharded cluster, changeStreamCursor.objsLeftInBatch() is expected to be 0 because of how router getMore command doesn't respect batchSize (this comment references SERVER-31992). However, based on the comment, if we do assert(changeStreamCursor.hasNext()); right before that assertion, the entire part should technically succeed. However, based on local testing, this assertion fails, i.e. the change stream only returns 4 docs although there are 5 updates.
- related to
-
SERVER-85389 Add jstests/change_streams passthrough testing for connecting to a replica set boostrapped as a single-shard cluster using replica set endpoint
- Closed
-
SERVER-87636 Investigate why change_streams hangs when run against a sharded cluster with embedded router
- Closed