[SERVER-33234] dropIndexes on mongos should ignore IndexNotFound from individual shards if some shard returned success Created: 09/Feb/18  Updated: 29/Oct/23  Resolved: 12/Feb/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.6.2, 3.7.1
Fix Version/s: 3.6.3, 3.7.2

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-31715 createIndexes (and dropIndexes) may n... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Sharding 2018-02-12, Sharding 2018-02-26
Participants:
Linked BF Score: 0

 Comments   
Comment by Githook User [ 13/Feb/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-33234 dropIndexes on mongos should ignore IndexNotFound from individual shards if some shard returned success

(cherry picked from commit f2e168877ab5efb45ec583ca3b4d05a423fe9d54)
Branch: v3.6
https://github.com/mongodb/mongo/commit/63eb274727e70752ceb76ed21fd6e4182bc4ddf4

Comment by Githook User [ 12/Feb/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-33234 dropIndexes on mongos should ignore IndexNotFound from individual shards if some shard returned success
Branch: master
https://github.com/mongodb/mongo/commit/f2e168877ab5efb45ec583ca3b4d05a423fe9d54

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