[SERVER-53448] Make ftdc_mirrored_reads.js resilient to slow machines Created: 18/Dec/20 Updated: 29/Oct/23 Resolved: 05/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0, 4.4.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Amirsaman Memaripour | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | save-for-luis, servicearch-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Service Arch 2021-05-17 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 29 | ||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
There are two assertions in the JS test for mirrored reads FTDC metrics (see here and here) that timeout after 5 seconds. On slow machines, querying FTDC metrics for the primary might take longer, resulting in failures. We should either increase the timeout or restructure the test to handle slow machines. |
| Comments |
| Comment by Githook User [ 17/Sep/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: (cherry picked from commit d628e4819eb75e4c9470cadadfdf062c3d2b0e5d) |
| Comment by Githook User [ 05/May/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |