Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9237#issuecomment-155247503
> I'm a little worried that disabling SO_REUSEADDR might cause ugly log
messages when you start applications back to back... aside from avoiding
inadvertently running into the issue being fixed here, is it really necessary?
Another approach to fix it is avoiding Spark to bind on `0.0.0.0`.
Otherwise, if some service binds to `0.0.0.0`, another service can bind to a
specified address with the same port.
---
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]
