[SERVER-62465] After intensities are updated, the resulting health check should run with the new values of intensities set. Created: 10/Jan/22 Updated: 29/Oct/23 Resolved: 11/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 4.4.13, 5.2.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kshitij Gupta | Assignee: | Kshitij Gupta |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.2, v4.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 50 | ||||||||
| Description |
|
Currently, we update the value of intensities to newValue after calling healthCheck(). If the timing is right, this can lead to a scenario where the resulting health check is a no-op (because the observer is seen as disabled) even if the check returns a failed status and the observer was just enabled. Further, another health check won't be scheduled and this observer will remain effectively disabled. To fix, we should call healthCheck() after updating to new intensity values so that the check uses the new values. |
| Comments |
| Comment by Githook User [ 15/Feb/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: (cherry picked from commit 0791c57fb7a3e86be3880aa926dfb9bb54f76802) |
| Comment by Githook User [ 11/Jan/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: (cherry picked from commit 0791c57fb7a3e86be3880aa926dfb9bb54f76802) |
| Comment by Githook User [ 10/Jan/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: |