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 resource ready (enough executors for receivers or satisfy the "minRegisteredResourcesRatio") Any suggestion is appreciated.
--- 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 if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org