Github user skonto commented on the issue:
https://github.com/apache/spark/pull/11157
@mgummelt I cleaned up the code ready for review. Right now if multiple
executors are run on the same host and there is some preconfigured port via
sparkConf like spark.blockManager.port then there will be conflicts resolved by
finding the next available port as it used to jappen before in spark code in
such cases.
---
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
