Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/17238
> If you aren't adding in machines to rack and configuring yarn properly
before adding it to your cluster that is a process issue you should fix on your
end
Actually, to play devil's advocate, the problem @morenn520 is describing is
a little more involved. You have a driver running, which has its own view of
what the cluster topology is, and then the cluster topology changes underneath
it. Deploying a new configuration on the new nodes being added does not fix the
driver, unless your "topology discovery script" is fully dynamic and always
goes to a central location to figure out what's the current topology.
So, basically, even if the new nodes know about the updated topology, the
existing driver instance might not, and there's no easy way to fix that I can
see.
(That being said, I haven't looked at the changes here.)
---
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
