-
Notifications
You must be signed in to change notification settings - Fork 28.8k
[SPARK-21559][Mesos] remove mesos fine-grained mode #18784
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@ArtRand @susanxhuynh pls review. |
Overall I trust your judgment if you think it's right to remove this, but I think it would have to wait for Spark 3.0? |
@srowen ok, yes. I have discussed this with Art and Suzan from Mesosphere and we made the decision to remove it as it is deprecated for so long. I am waiting for their comments here. |
Test build #80072 has finished for PR 18784 at commit
|
ce11906
to
7dc41d0
Compare
Fixed the test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is only needed in the fine-grained case as it is the only case where the executor was killed in TaskSchedulerImpl. I am keeping the TaskStatus.LOST definition as it is propagated back from mesos processes to TaskSchedulerImpl.
7dc41d0
to
2c1574e
Compare
@srowen I made a new commit but didn't get a new build... |
Test build #80079 has finished for PR 18784 at commit
|
@srowen this test https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80079/ seems flaky, I run the suite locally and works fine (13 tests finished successfully). |
Jenkins, retest this please. |
Test build #80087 has finished for PR 18784 at commit
|
@ArtRand @susanxhuynh pls review. |
@skonto @ArtRand @susanxhuynh Do we still want this? |
@jiangxb1987 yes. I'll work to review this ASAP. |
I work with @ArtRand and @susanxhuynh Fine grained mode has been deprecated for a while. If it is standard procedure to wait till next release and if that is 3.0 we should wait till Spark 3.0 release. @skonto @srowen |
Test build #87876 has finished for PR 18784 at commit
|
Let's remove it in 3.0 then. We can do it after 2.4 release. |
@rxin I will update the PR. |
Go for it.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@skonto also cool by me. If you resolve the merge conflict, let's do it.
"fine-grained" (deprecated). | ||
|
||
## Coarse-Grained | ||
Spark runs over Mesos in "coarse-grained" mode. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might add a note here that fine-grained was removed in 3.0.0
private[this] val shutdownTimeoutMS = | ||
conf.getTimeAsMs("spark.mesos.coarse.shutdownTimeout", "10s") | ||
.ensuring(_ >= 0, "spark.mesos.coarse.shutdownTimeout must be >= 0") | ||
conf.getTimeAsMs("spark.mesos.shutdownTimeout", "10s") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this property name change need to be reflected in docs? I wasn't sure.
@skonto do you want to proceed with this? |
Looks inactive. @srowen and @felixcheung, do you know anyone who might be interested in this? |
@srowen @HyukjinKwon sorry missed the msg, yes I will spend some cycles to fix it. |
Ping? If you won't update this, please close so someone else can pick it up. |
let's do it! |
Ok let me see what I can update before closing. |
closing. |
Don’t we want this?
|
What changes were proposed in this pull request?
Removes mesos fine-grained mode. Specifically:
How was this patch tested?
Tested with the integration test suite here:
https://github.com/typesafehub/mesos-spark-integration-tests