Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16691
I don't like copying codes from Spark core. Maybe let's still keep using a
dummy Spark job.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16691
cc @tdas also
---
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, or
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16691
@zsxwing That is right, this pr is the improvement for the previous one.
There is no much performance regression, i.e. only wait for
"spark.scheduler.maxRegisteredResourcesWaitingTime" for
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16691
I don't think all cases need to wait for all resources ready. That's why
`spark.scheduler.minRegisteredResourcesRatio` is added to allow the user
changing the behavior.
---
If your project is set
