Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-62465

After intensities are updated, the resulting health check should run with the new values of intensities set.

    • Fully Compatible
    • ALL
    • v5.2, v4.4
    • 50

      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.

            kshitij.gupta@mongodb.com Kshitij Gupta
            kshitij.gupta@mongodb.com Kshitij Gupta
            0 Vote for this issue
            2 Start watching this issue