[SERVER-37284] ndeleted:0 is logged/profiled when the number of deleted documents is not known Created: 24/Sep/18 Updated: 29/Oct/23 Resolved: 13/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.6 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
|||||||||||||
| Assigned Teams: |
Query
|
|||||||||||||
| Backwards Compatibility: | Fully Compatible | |||||||||||||
| Operating System: | ALL | |||||||||||||
| Steps To Reproduce: | Run this from one shell:
Then use db.currentOp() and db.killOp() to kill the multi-delete operation from another shell. |
|||||||||||||
| Sprint: | Query 2018-12-17, Query 2018-12-31 | |||||||||||||
| Participants: | ||||||||||||||
| Description |
|
The ndeleted stat is filled out twice. First, we set it to zero at the beginning of a delete op: Then, we set it to the actual number of deleted documents at the end: Setting the statistic to zero has the adverse consequence of causing the system to log/profile ndeleted:0 when the actual number of deleted documents is unknown. I believe this line of code is superfluous and can be removed. |
| Comments |
| Comment by Githook User [ 13/Dec/18 ] |
|
Author: {'username': 'bLamarche413', 'email': 'thesisiwbl@gmail.com', 'name': 'Brigitte Lamarche'}Message: |