[SERVER-35840] dropDatabase may log a confusing number of collection drops Created: 27/Jun/18 Updated: 29/Oct/23 Resolved: 31/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kelsey Schubert | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||
| Steps To Reproduce: | Observed on 3.6.5 on macOS
In the logs:
|
||||||||||||
| Sprint: | Storage NYC 2018-12-31, Storage NYC 2019-01-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
I believe that if a collection is dropped very quickly as part of dropDatabase, we do not count it in the dropDatabase command. This can confuse some users since we may log that no collections were dropped. We could either make this number always accurate or clarify what metric it is tracking. |
| Comments |
| Comment by Githook User [ 31/Dec/18 ] |
|
Author: {'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'name': 'Gregory Wlodarek'}Message: |