You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't find any error logs in the spark-history-server pod, but it keeps restarting.
I want to change the logging level to DEBUG to identify the root cause.
I tried doing this, but it didn't work.
-Dlog4j.rootCategory=DEBUG,console
The text was updated successfully, but these errors were encountered:
I resolved this issue by creating a custom image based on varabonthu/spark-web-ui:1.0.6.
I added a custom log4j.properties file to /spark/opt/conf, which allowed me to identify the root cause of the problem.
The issue stems from the fact that we're not permitted to access S3 via the public network, but the system attempts to connect to S3 using the *.s3.amazonaws.com domain.
Caused by: java.net.UnknownHostException: BUCKET_NAME.s3.amazonaws.com: Name or service not known
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929)
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324)
at java.net.InetAddress.getAllByName0(InetAddress.java:1277)
at java.net.InetAddress.getAllByName(InetAddress.java:1193)
at java.net.InetAddress.getAllByName(InetAddress.java:1127)
at com.amazonaws.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:27)
at com.amazonaws.http.DelegatingDnsResolver.resolve(DelegatingDnsResolver.java:38)
at com.amazonaws.thirdparty.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:112)
at com.amazonaws.thirdparty.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376)
To access S3 via a VPC Endpoint, I added the following option to sparkHistoryOpts:
I couldn't find any error logs in the spark-history-server pod, but it keeps restarting.
I want to change the logging level to DEBUG to identify the root cause.
I tried doing this, but it didn't work.
The text was updated successfully, but these errors were encountered: