[SERVER-51490] aggregate_operation_metrics.js should clear metrics after waiting for replication Created: 12/Oct/20 Updated: 29/Oct/23 Resolved: 12/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| 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: | Execution Team 2020-10-19 | ||||
| Participants: | |||||
| Linked BF Score: | 20 | ||||
| Description |
|
Before running the first aggregation query, and immediately after waiting for replication, clear the operation metrics. If a secondary is slow to replicate the drop of "newDB" in the test, then it will be reported in the metrics earlier on than it should, causing the test to fail. |
| Comments |
| Comment by Githook User [ 12/Oct/20 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}Message: |