Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1019#issuecomment-46476269
@ash211 now that we don't log the exception, we should improve the logging
that spark does when this happens. I can think of a few simple improvements
here.
1. We should log the new port that we are going to try on instead of just
saying "Trying again"
2. The first line should be logged at WARN level, not Info.
3. If the exception message contains "Address already in use" we can just
log the exception message at WARN.
4. If the exception is some other message, we should log it at ERROR, and
pass the exception to `logError` so that the entire stack trace is printed.
---
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.
---
