Github user viirya commented on the issue:
https://github.com/apache/spark/pull/9433
Seems no interest from you for this. Close this now.
---
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
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/9433
@kayousterhout Any ideas on this?
---
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
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/9433
ping @kayousterhout
---
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,
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/9433
@kayousterhout About the issue that this may make the scheduling policy
harder to reason about and confuse others. I think we can disable this by
default (by using Long.MaxValue as default waiting
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9433
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/9433
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60484/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9433
**[Test build #60484 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60484/consoleFull)**
for PR 9433 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/9433
@kayousterhout Sorry for replying late.
For your first concern, that is the job A might not want to waste on
non-local executor and is more like to wait spark.locality.wait for local
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/9433
**[Test build #60484 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60484/consoleFull)**
for PR 9433 at commit
