Skip to content
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

Let director manage java #58

Open
TobyHFerguson opened this issue May 23, 2018 · 0 comments
Open

Let director manage java #58

TobyHFerguson opened this issue May 23, 2018 · 0 comments

Comments

@TobyHFerguson
Copy link
Owner

Director can now handle the complete installation of java, including policy files, as per the below email. We should leverage this and reduce the code we maintain:

If you are using the DIRECTOR_MANAGED or AUTO Java installation strategy, then you will get the unlimited strength JCE policy files on the CM instance and all cluster instances if you specify "unlimitedJce: true" in the cloudera-manager section of the configuration file. See the example here:

https://www.cloudera.com/documentation/director/latest/topics/director_create_kerberized_cluster.html

If you are using the NONE Java installation strategy, then it's up to you to get the policy files in place, as in Mubashir's example. It's also up to you to get the JDK installed in the first place.

For more on the different Java installation strategies:

https://www.cloudera.com/documentation/director/latest/topics/director_create_java_clusters.html

Director and the example bootstrap script for installing JDK 8 don't include the policy files by default because of prior concerns about the legality of putting them in place by default in some jurisdictions. Interestingly, starting in Java 8u162 and Java 9, the unlimited policy files are in place and enabled by default, so all of this becomes moot (but still works).

https://golb.hplar.ch/2017/10/JCE-policy-changes-in-Java-SE-8u151-and-8u152.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant