[SERVER-34796] Make _cleanup only clear the DSS if the db exists Created: 02/May/18  Updated: 29/Oct/23  Resolved: 14/May/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.9
Fix Version/s: 4.0.0

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
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-34658 Don't throw an exception inside a Sco... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-05-21
Participants:
Linked BF Score: 34

 Description   

If movePrimary fails, we call cleanupOnError which calls _cleanup. Currently we throw "ConflictingErrorInProgress" in _cleanup if the db doesn't exist. We should change this so that we only clear the dss if the dbexists, rather than throwing this error. If the db hasn't been created or if it has been dropped, there is nothing to clear.



 Comments   
Comment by Githook User [ 14/May/18 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-34796 Make _cleanup in movePrimary only clear the DSS if the db exists
Branch: master
https://github.com/mongodb/mongo/commit/06f338d1c9bdce2f5eecd4162a0200eb8c444571

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