[SERVER-53594] Allow collections and databases to be dropped in standalone mode with unfinished replicated index builds Created: 05/Jan/21 Updated: 29/Oct/23 Resolved: 17/Oct/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.3 |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vitalii K. | Assignee: | Shin Yee Tan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
MongoDB Standalone Server with authorization. Proxmox, Ubuntu LXC container. No LSB modules are available. db version v4.4.3 } Problem Descriptionthere were 20 collections in the current database; 3 are not deleted, error; after an attempt to delete, there is no way to connect to the database; only restart helps |
| Comments |
| Comment by Githook User [ 14/Oct/22 ] | |||||||
|
Author: {'name': 'Shin Yee Tan', 'email': 'shinyee.tan@mongodb.com', 'username': 'shinyeet'}Message: | |||||||
| Comment by Eric Sedor [ 12/Jan/21 ] | |||||||
|
Understood vkatochka@protonmail.com, we'll keep this ticket open for now in case this comes up again soon. Thank you! | |||||||
| Comment by Vitalii K. [ 12/Jan/21 ] | |||||||
|
The Replica Set was modified two months ago. Now there is no way to do this on this server. I'll try to replicate this from scratch on another server, can't promise when. | |||||||
| Comment by Eric Sedor [ 06/Jan/21 ] | |||||||
|
Thanks vkatochka@protonmail.com, that seems to reinforce Louis's suspicion that an index build may have been interrupted by transitioning from a replica set to standalone mode. We're interested in addressing this as a bug. Can you let us know if you can: 1) restart the node as a replica set If this doesn't work can you provide a complete log file covering these activities, as well as archive (tar or zip) of the $dbpath/diagnostic.data directory (the contents are described here)? Thanks! | |||||||
| Comment by Vitalii K. [ 06/Jan/21 ] | |||||||
|
Mmm ... I have a standalone server running with no replica set. But when starting mongo shell (when there was an error) I was getting the following message: Previously, some work was done related to oplog and possibly some options related to replSet were included. And it is possible that collections and indexes were created during this period. | |||||||
| Comment by Louis Williams [ 05/Jan/21 ] | |||||||
|
Hi vkatochka@protonmail.com, thanks for filing this bug report. Did you by any chance start an index build while the node was in a replica set and shut it down before the index build finished? If so, you should also be able to drop the database (without crashing) if you restart the node as a replica set member again (with --replSet). | |||||||
| Comment by Vitalii K. [ 05/Jan/21 ] | |||||||
|
After dropping the index from the collection, the collection was dropped successfully. | |||||||
| Comment by Vitalii K. [ 05/Jan/21 ] | |||||||
|
tried to delete db
|