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.

Possible issue from CM with linux-container, native libs, JNI and env settings

Possible issue from CM with linux-container, native libs, JNI and env settings

New Contributor

Hi,

 

I don't where I can declare possible issue from CM.

 

I had some issues after I deployed a YARN cluster with the jni adaptator for groups resolution/mapping.

jni group resolution used native libs. Yarn containers didn't start because, jni native lib wasn't found by during the loading (launch-containers.sh).

 

Actually, native lib are referenced in CM by LD_LIBRARY_PATH variable and the default value is something like  

LD_LIBRARY_PATH=...:$HADOOP_COMMON_PATH/lib/native

 

But, if I check containers-launch.sh script, export HADOOP_COMMON_PATH is set after the LD_LIBRARY_PATH export.

So, native libs aren't loaded and the container failed (exit code 1).

 

I made a workaround, I don't if the issue comes from CM or YARN project.

 

Maybe this issue can interest someone else.

 

Regards, Guillaume