Member since
07-29-2013
11
Posts
3
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8890 | 12-12-2013 09:17 AM |
07-22-2015
11:10 AM
Hello! I'd guess that you are not in the US, and that you have locale (e.g., LC_ALL) environment variables set. You're running into https://issues.cloudera.org/browse/IMPALA-2014. In the meantime, as a workaround, place "LC_ALL=C" into the configuration "Impala Service Environment Advanced Configuration Snippet (Safety Valve)". Please do report back if that works as a workaround for you! Thanks! -- Philip
... View more
12-12-2013
09:17 AM
2 Kudos
Hi ge-ko, Cloudera Manager generally has a strategy to pick which Java version to use. The Host Inspector is intended for the common case: people only have one Java installed, and we want to make sure that CM can find good, consistent versions of Java. If you want to dig into the details, /usr/lib64/cmf/service/common/cloudera-config.sh and /usr/lib/bigtop-utils/bigtop-detect-javahome might be of interest. If you're customizing JAVA_HOME, you have two options: you can do it service-by-service with safety valves. That works, but Host Inspector won't know about it. That's ok. You can also edit JAVA_HOME by editing /etc/default/cloudera-scm-agent. See https://www.cloudera.com/content/cloudera-content/cloudera-docs/CM4Ent/latest/Cloudera-Manager-Installation-Guide/cmig_java_home_location.html for more details. -- Philip
... View more