Github user liutang123 commented on the issue:
https://github.com/apache/spark/pull/19812
Sorry, I can not reproduce it now. But, sometimes,
`ExecutorAllocationManager ` did not request new executors and
`YarnSchedulerBackend.requestedTotalExecutors` is 0. I will close this PR now
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19812
Does this failure ". For some reason, all of the 3 executors failed. "
happened during task running or before task submission? Besides, if you're
running on yarn, yarn will bring new executors to
Github user liutang123 commented on the issue:
https://github.com/apache/spark/pull/19812
Hi @jerryshao , I modified the info of this PR.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/19812
Hi @liutang123 would you mind explaining us the issue you met and how to
reproduce it? Currently we don't know what actual issue it is and how to
evaluate your changes.
---
Github user liutang123 commented on the issue:
https://github.com/apache/spark/pull/19812
@srowen Would you please look at this when you have time?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
Github user liutang123 commented on the issue:
https://github.com/apache/spark/pull/19812
Jenkins, retest this please
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/19812
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
