[SERVER-74839] investigation/test will change stream getMores be rejected correctly before data is deleted after a split/merge Created: 14/Mar/23  Updated: 03/Apr/23  Resolved: 03/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Mickey Winters Assignee: Backlog - Query Execution
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Participants:

 Description   

getMores are not denied like other read commands https://github.com/mongodb/mongo/blob/d0a7b4e6b3c4ae2d356ce23996ecf3f7ed56ad9b/src/mongo/db/repl/tenant_migration_donor_access_blocker.cpp#L58
in fact we also have tests to ensure getMores aren't rejected after a commit https://github.com/mongodb/mongo/blob/a9684a6176388f095a6a2b7857c042a89bf56530/jstests/serverless/shard_split_read_your_own_writes.js#L56

this is an issue because if the collections are dropped getMores might be rejected with cursorKilled (nonResumable) instead of TennantMigrationCommitted (resumable)



 Comments   
Comment by Mickey Winters [ 03/Apr/23 ]

we decided that a reasonable client would have issued a getMore before getting to this point so we are not looking further into fixing this case

Generated at Thu Feb 08 06:28:40 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.