Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/19303
Personally I don't suggest we add extra logic to resolve a non-bug.
---
-
To unsubscribe, e-mail:
Github user 10110346 commented on the issue:
https://github.com/apache/spark/pull/19303
yes,it is no problemï¼this is just an optimization.
You are right,it is standalone mode
---
-
To unsubscribe, e-mail:
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19303
IIUC, if there's no core left, requesting new executors should be a no-op,
am I right? So there should be no problem even without your fix?
From your patch, it looks like you're putting
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19303
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/82023/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19303
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19303
**[Test build #82023 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/82023/testReport)**
for PR 19303 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/19303
**[Test build #82023 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/82023/testReport)**
for PR 19303 at commit
