Description
Since we haven't fixed SPARK-3332 (the issue where tags aren't a safe strategy for determining spark-ec2 cluster membership), let's revert SPARK-2333 in branch-1.2.
I'm filing a blocker JIRA for this so that we don't forget to do this before cutting a 1.2.0 release candidate. Unfortunately, the patch doesn't cleanly revert, so this may take a bit of work to do correctly.
Attachments
Issue Links
- relates to
-
SPARK-3332 Tagging is not atomic with launching instances on EC2
- Closed
- links to