Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Ignored Java option due to Java 8.0

Solved Go to solution

Ignored Java option due to Java 8.0

New Contributor

Hello,

It seems that Java some option (MaxPermSize), which is used for several of the hadoop commands, is not available any more since Java 8.0. For example, one gets the info message from the end of this message when starting beeline from the command line.
I don't know if this will cause any trouble later on.


node-07:~ # beeline
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; support was removed in 8.0
Beeline version 1.1.0-cdh5.5.1 by Apache Hive
beeline>

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: Ignored Java option due to Java 8.0

Master Guru
If you've previously set manual overrides to MaxPermSize options in your
configurations, you can remove them away safely having switched to using
JDK8. If you still have parts that use JDK7, leave them be and ignore the
warning.

The warnings themselves do not pose a problem, as JDK8 will simply note
that it won't be using them anymore and continue to start up normally.
However, a future Java version (JDK9 or 10) may choose to interpret it as
an invalid command and fail. Read more on this JDK level change at
https://dzone.com/articles/java-8-permgen-metaspace
1 REPLY 1
Highlighted

Re: Ignored Java option due to Java 8.0

Master Guru
If you've previously set manual overrides to MaxPermSize options in your
configurations, you can remove them away safely having switched to using
JDK8. If you still have parts that use JDK7, leave them be and ignore the
warning.

The warnings themselves do not pose a problem, as JDK8 will simply note
that it won't be using them anymore and continue to start up normally.
However, a future Java version (JDK9 or 10) may choose to interpret it as
an invalid command and fail. Read more on this JDK level change at
https://dzone.com/articles/java-8-permgen-metaspace