[SERVER-42380] inMemory can't use db.dropDatabase() to drop the db Created: 24/Jul/19 Updated: 27/Oct/23 Resolved: 04/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.0.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew zhou | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
MongoDB server version: 4.0.10,MongoDB Enterprise |
||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 24/Jul/19 ] |
|
My apologies, this is in fact not a bug. As mentioned in our documentation on the In-Memory storage engine, you must set writeConcernMajorityJournalDefault to false in the replica set config for any cluster with voting nodes that use the In-Memory storage engine. If you do so, the drops should complete successfully. Can you please do so and confirm that the drop now works? |
| Comment by Danny Hatcher (Inactive) [ 24/Jul/19 ] |
|
Thanks for the report. I've confirmed that db.dropDatabase() does not work against the inMemory storage engine. I'm forwarding this to the appropriate team to take a closer look. |