[SERVER-53282] Handle collection drop mid-query-stage in TenantCollectionCloner Created: 08/Dec/20  Updated: 29/Oct/23  Resolved: 29/Jan/21

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

Type: Task Priority: Major - P3
Reporter: Vesselina Ratcheva (Inactive) Assignee: Vesselina Ratcheva (Inactive)
Resolution: Fixed Votes: 0
Labels: pm-1791_milestone-B
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53724 Make DBClient able to reauthenticate ... Closed
Related
related to SERVER-52717 Handle resuming after failover in Ten... Closed
related to SERVER-52897 Handle collection drop in TenantColle... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2021-01-11, Repl 2021-01-25, Repl 2021-02-08
Participants:

 Description   

Handling NamespaceNotFound during the query stage requires resuming after processing other errors (like QueryPlanKilled). This is probably doable through the cloner alone (like in initial sync), but may have something to do with the work in SERVER-52717.



 Comments   
Comment by Githook User [ 29/Jan/21 ]

Author:

{'name': 'Vesselina Ratcheva', 'email': 'vesselina.ratcheva@10gen.com', 'username': 'vessy-mongodb'}

Message: SERVER-53282 Handle collection drop mid-query-stage in TenantCollectionCloner
Branch: master
https://github.com/mongodb/mongo/commit/0abea0b18b183051b7ef47d9b86056d304157dcf

Generated at Thu Feb 08 05:30:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.