Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/15588
I think this fix cannot really handle this imbalance receiver allocation
problem, also blindly waste the CPU time.
What @lw-lin mentioned is a feasible solution to wait for executors to be
registered, also `ReceiverSchedulingPolicy` should probably handle this problem
well, but strictly even distribution is hard to guarantee and very costing
especially when a cluster has intensive resource contention.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
