Github user d2r commented on the issue:
https://github.com/apache/spark/pull/17500
> I get it, though I'm still not sure it's a great solution to artificially
open and close the socket just for this. Is there no other way to probe whether
a port is available or is that about the best one can do, to actually try to
open it?
As far as I am aware, the best we can do is try to bind the port.
> log4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERROR
This works. There was an oversight on our part due to a merge error that we
did not pick up this change when the jetty components were shaded. So I will
close this pull request and close the jira as well.
@srowen Thanks for looking.
---
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]
