[SERVER-30521] in syncApply, throw NamespaceNotFound rather than returning a status on missing database Created: 04/Aug/17  Updated: 30/Oct/23  Resolved: 09/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-30293 in syncApply, throw NamespaceNotFound... Closed
related to SERVER-33160 syncApply() treatment of delete opera... Closed
is related to SERVER-30220 Lock correct nss for syncApply by UUID Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-08-21
Participants:
Linked BF Score: 0

 Description   

Introduced in the same commit that introduced SERVER-30293 (https://github.com/mongodb/mongo/commit/9d8bc8dc6c8d1dc92bbf466f27783464ed4f5704), we just missed this case when fixing SERVER-30293



 Comments   
Comment by Githook User [ 09/Aug/17 ]

Author:

{'name': 'Judah Schvimer', 'username': 'judahschvimer', 'email': 'judah@mongodb.com'}

Message: SERVER-30521 in syncApply, throw NamespaceNotFound rather than returning a status on missing database
Branch: master
https://github.com/mongodb/mongo/commit/eaee6e57a07fd19874bd3116ea5809174eaef1ac

Comment by Spencer Brody (Inactive) [ 07/Aug/17 ]

Since Geert's on vacation for the next 3 weeks, Judah can you take over fixing this?

Generated at Thu Feb 08 04:24:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.