Uploaded image for project: 'Spark'
  1. Spark
  2. SPARK-3332

Tagging is not atomic with launching instances on EC2

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.1, 1.2.0
    • Component/s: EC2
    • Labels:
      None

      Description

      The implementation for SPARK-2333 changed the machine membership mechanism from security groups to tags.

      This is a fundamentally flawed strategy as there aren't guarantees at all the machines will have a tag (even with a retry mechanism).

      For instance, if the script is killed after launching the instances but before setting the tags the machines will be "invisible" to a destroy command, leaving a unmanageable cluster behind.

      The initial proposal is to go back to the previous behavior for all cases but when the new flag (--security-group-prefix) is used.

      Also it's worthwhile to mention that SPARK-3180 introduced the --additional-security-group flag which is a reasonable solution to SPARK-2333 (but isn't a full replacement to all use cases of --security-group-prefix).

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                joshrosen Josh Rosen
                Reporter:
                douglaz Allan Douglas R. de Oliveira
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: