Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11644#issuecomment-195248388
I like the principle, but passing around an error message as an arg to
`SparkEnv` makes this tiny aspect leak too much into the API. If it's just to
be able to report which config to change, I think I wouldn't do that.
Generically advise changing a port config. This would be much simpler then,
commensurate with the scope of the change.
---
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
