-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spark benchmarks broken by JDK-8296244 #439
Comments
Thanks for the report! To be completely honest, the JDK bug info you reference does not make any sense to me (I never really needed to fiddle with security manager and I was under impression that security manager is actually going away, not that it's going to cause more problems :-) Is there some transition guide (or a reasonable default setting for the java.security.manager property) on how to unbreak apps/frameworks that JDK cleanups/enhancements keep breaking (Spark in particular)? |
I'm not aware of any particular guide apart from deprecation warnings that more recent versions of javac must be emitting when compiling Spark code that used deprecated API. It might be worth encouraging Spark maintainers to periodically look at these warnings and plan for addressing them. |
I'm from Oracle's Java Platform Group. Many thanks for trying out the jdk23 early builds and reporting this issue. The |
Just to add to Weijun's comment. Subject.getSubject(ACC) has been deprecated for removal since Java 17. Developers are encouraged to move to the replacement Subject.current(). I think we should make sure there is an issue in the Hadoop issue tracker for this. |
Thanks for the links!
Great! This might be just what's needed for Renaissance. I'll check if we can setup the right environment for Spark in the harness so that its calls to Hadoop do not fail on this. |
As a result of JDK-8296244 some/all Spark benchmarks in renaissance are broken:
As far as I can see, any app that does not explicitly set the java.security.manager system property can no longer call
javax.security.auth.Subject.getSubject()
.The text was updated successfully, but these errors were encountered: