aboutsummaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorXiangrui Meng <meng@databricks.com>2014-11-25 16:07:09 -0800
committerAndrew Or <andrew@databricks.com>2014-11-25 16:07:20 -0800
commita48ea3cef22687694a4471705fb707bd1e8fa592 (patch)
tree7b6912b6301ea53fce27cf3d2b28bf4dad1f30d9 /NOTICE
parent93b914df1566c6359d8f1546ab7344823dc4341f (diff)
downloadspark-a48ea3cef22687694a4471705fb707bd1e8fa592.tar.gz
spark-a48ea3cef22687694a4471705fb707bd1e8fa592.tar.bz2
spark-a48ea3cef22687694a4471705fb707bd1e8fa592.zip
[Spark-4509] Revert EC2 tag-based cluster membership patch
This PR reverts changes related to tag-based cluster membership. As discussed in SPARK-3332, we didn't figure out a safe strategy to use tags to determine cluster membership, because tagging is not atomic. The following changes are reverted: SPARK-2333: 94053a7b766788bb62e2dbbf352ccbcc75f71fc0 SPARK-3213: 7faf755ae4f0cf510048e432340260a6e609066d SPARK-3608: 78d4220fa0bf2f9ee663e34bbf3544a5313b02f0. I tested launch, login, and destroy. It is easy to check the diff by comparing it to Josh's patch for branch-1.1: https://github.com/apache/spark/pull/2225/files JoshRosen I sent the PR to master. It might be easier for us to keep master and branch-1.2 the same at this time. We can always re-apply the patch once we figure out a stable solution. Author: Xiangrui Meng <meng@databricks.com> Closes #3453 from mengxr/SPARK-4509 and squashes the following commits: f0b708b [Xiangrui Meng] revert 94053a7b766788bb62e2dbbf352ccbcc75f71fc0 4298ea5 [Xiangrui Meng] revert 7faf755ae4f0cf510048e432340260a6e609066d 35963a1 [Xiangrui Meng] Revert "SPARK-3608 Break if the instance tag naming succeeds" (cherry picked from commit 7eba0fbe456c451122d7a2353ff0beca00f15223) Signed-off-by: Andrew Or <andrew@databricks.com>
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions