Github user ksakellis commented on the pull request:
https://github.com/apache/spark/pull/3486#issuecomment-66376138
@andrewor14 The reason for this approach is that it is really not yarn
specific. I was envisioning adding support for standalone mode this way too.
This is why the logURL information is passed in through the environment
variables and back to the scheduler backend. I didn't want to make specific
modifications to the yarn AM. I also wanted to avoid special casing yarn client
and cluster modes.
In general, I think having an event when an executor was added is useful -
we can add more information in the ExecutorInfo structure in the future to
expose more information about the specific executor that was added.
---
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]
