Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-15936

Terminate cloud hosts that have already-terminated intent hosts

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • current_quarter
    • plt
    • None

    Description

      Most of the cloud providers have a check in TerminateInstances that prevents a host from being terminated when it's already in the "terminated" state. However, some hosts can be marked as terminated in the DB but still alive in AWS. The expected treatment of these live hosts is that they should be actually be terminated in the cloud to match their DB state (relying on the reaper to clean up resources is not a desirable solution). The checks for terminated hosts in the cloud providers should be removed to allow hosts to be re-terminated in TerminateInstances.

       

      Alternatively, the logic of terminating cloud hosts with terminated intent hosts can be modified. For example, if the intent host is terminated and the cloud host's agent later checks in, the intent host can be converted to a decommissioned real host so that TerminateInstances occurs without needing to remove the check for already-terminated hosts in the cloud provider implementations.

      Attachments

        Issue Links

          Activity

            People

              kimberly.tao@mongodb.com Kim Tao
              kimberly.tao@mongodb.com Kim Tao
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: