-
Notifications
You must be signed in to change notification settings - Fork 28.9k
Added a TaskSetManager unit test. #1024
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
This test ensures that (as an optimization), when there are no alive executors that satisfy a particular locality level, the TaskSetManager doesn't ever use that as the maximum allowed locality level (this optimization ensures that a job doesn't wait extra time in an attempt to satisfy a scheduling locality level that is impossible).
|
Merged build triggered. |
|
Merged build started. |
|
Merged build finished. |
|
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15570/ |
|
Jenkins, retest this please |
|
Merged build triggered. |
|
Merged build started. |
|
Thanks for adding this, Kay. Please merge it assuming it passes Jenkins. |
|
Merged build finished. All automated tests passed. |
|
All automated tests passed. |
|
I've merged this into master. |
This test ensures that when there are no alive executors that satisfy a particular locality level, the TaskSetManager doesn't ever use that as the maximum allowed locality level (this optimization ensures that a job doesn't wait extra time in an attempt to satisfy a scheduling locality level that is impossible). @mateiz and @lirui-intel this unit test illustrates an issue with apache#892 (it fails with that patch). Author: Kay Ousterhout <[email protected]> Closes apache#1024 from kayousterhout/scheduler_unit_test and squashes the following commits: de6a08f [Kay Ousterhout] Added a TaskSetManager unit test.
This test ensures that when there are no alive executors that satisfy a particular locality level, the TaskSetManager doesn't ever use that as the maximum allowed locality level (this optimization ensures that a job doesn't wait extra time in an attempt to satisfy a scheduling locality level that is impossible). @mateiz and @lirui-intel this unit test illustrates an issue with apache#892 (it fails with that patch). Author: Kay Ousterhout <[email protected]> Closes apache#1024 from kayousterhout/scheduler_unit_test and squashes the following commits: de6a08f [Kay Ousterhout] Added a TaskSetManager unit test.
* upgrade spark call home 0.2.8 * fix the brace issue
This reverts commit 8c6a5f1.
…2.0 (apache#1024) Co-authored-by: Egor Krivokon <>
…2.0 (apache#1024) Co-authored-by: Egor Krivokon <>
This test ensures that when there are no
alive executors that satisfy a particular locality level,
the TaskSetManager doesn't ever use that as the maximum
allowed locality level (this optimization ensures that a
job doesn't wait extra time in an attempt to satisfy
a scheduling locality level that is impossible).
@mateiz and @lirui-intel this unit test illustrates an issue
with #892 (it fails with that patch).