[SERVER-30293] in syncApply, throw NamespaceNotFound rather than returning a status Created: 24/Jul/17  Updated: 30/Oct/23  Resolved: 25/Jul/17

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

Type: Bug Priority: Major - P3
Reporter: Geert Bosch Assignee: Geert Bosch
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-33160 syncApply() treatment of delete opera... Closed
is related to SERVER-30220 Lock correct nss for syncApply by UUID Closed
is related to SERVER-30521 in syncApply, throw NamespaceNotFound... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage 2017-07-31
Participants:
Linked BF Score: 0

 Description   

The special logic of ignoring NamespaceNotFound during initial sync, where replaying the oplog should be idempotent, requires throwing exceptions for this error condition rather than returning a status.



 Comments   
Comment by Githook User [ 25/Jul/17 ]

Author:

{'email': 'geert@mongodb.com', 'username': 'GeertBosch', 'name': 'Geert Bosch'}

Message: SERVER-30293 Throw instead of return NamespaceNotFound
Branch: master
https://github.com/mongodb/mongo/commit/68bca92abdd01a91dd3606cc3f5708f74d084b86

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