You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by douglaz <gi...@git.apache.org> on 2014/08/31 22:57:01 UTC
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
GitHub user douglaz opened a pull request:
https://github.com/apache/spark/pull/2223
SPARK-3332 - Tags shouldn't be the main strategy for machine membership on clusters
See the issue for more information. Also removed a redundant entry for t1.micro.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/douglaz/spark machine_membership
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/2223.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2223
----
commit 065b7d2cf506344e63fc7ab47a42838adac389e9
Author: Allan Douglas R. de Oliveira <al...@chaordicsystems.com>
Date: 2014-08-31T20:10:37Z
Also use the group name as machine membership and other small cleanups
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
Posted by JoshRosen <gi...@git.apache.org>.
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2223#issuecomment-67395557
We ended up reverting the tag-based cluster membership patch for both the 1.1. and 1.2 releases, and we've also committed the revert to `master` in #3453, so I think we can close this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
Posted by SparkQA <gi...@git.apache.org>.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2223#issuecomment-54694356
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
Posted by pwendell <gi...@git.apache.org>.
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/2223#issuecomment-54002619
I posted some feedback on this in the JIRA. There is a reason we moved away from security groups, so it's not an obvious choice to just revert this. But I agree we should punt this to the 1.2 timeframe and decide then
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2223
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org
[GitHub] spark pull request: SPARK-3332 - Tags shouldn't be the main strate...
Posted by AmplabJenkins <gi...@git.apache.org>.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2223#issuecomment-54001020
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org