[SERVER-49144] Don't remove({}) large collections in batch_write_command_insert.js Created: 26/Jun/20 Updated: 29/Oct/23 Resolved: 28/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| 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 | ||||
| Sprint: | Repl 2020-07-13, Repl 2020-07-27, Repl 2020-08-10 | ||||
| Participants: | |||||
| Linked BF Score: | 15 | ||||
| Description |
|
In batch_write_command_insert.js, we use remove({}) to get a collection back to its initial empty state. If the collection has a lot of elements in it (and we do at one point), then we end up deleting them all one by one on the secondaries, which puts a lot of load on the test infrastructure and causes spurious failures. We should drop the collection rather than remove({}) unless there's a good reason to do otherwise. It appears the remove({}) has been there since the test was created. |
| Comments |
| Comment by Githook User [ 27/Jul/20 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com', 'username': 'mtrussotto'}Message: |