Github user srowen 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?
I see
`log4j.logger.org.spark_project.jetty.util.component.AbstractLifeCycle` in our
log4j properties files, so clearly this is intended to be silenced by log
config already. Is that not taking effect? if you haven't changed anything then
clearly it isn't. I wonder if for some reason the unshaded package's logger
needs to be configured, if so?
`log4j.logger.org.eclipse.jetty.util.component.AbstractLifeCycle=ERROR`
---
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]
