Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
None
-
None
-
None
Description
For reasons unknown this doesn't seem to be working anymore. I deleted my log4j.properties file and did a fresh build and it noticed it still gave me a verbose stack trace when port 4040 was contented (which is a log we silence in the conf). I actually think this was an issue even before sowen's changes, so not sure what's up.
Attachments
Issue Links
- relates to
-
SPARK-2913 Spark's log4j.properties should always appear ahead of Hadoop's on classpath
- Resolved