Hello @JB0000000000001,   If you added the Impala Service after Hue was part of the cluster, it is likely you need to manually enable Impala via Cloudera Manager.   Try going to Hue --> Configuration Then, search for "Impala Service"   If "none" is selected, choose the name of your Impala service instead and save. Restart Hue. Log out of Hue and back in if you already have an active session just to be sure.   After that, Impala service should be available in Hue.     ... View more

@epowell, Yes, you are correct.  Client Configurations are managed separately from the configurations that servers use when CDH is managed by Cloudera Manager.  Deploy Client Configuration for your cluster to make sure the /etc/hadoop/conf files contain the latest configuration items.  Once that is done, you should be able to run commands just fine.   Ben ... View more

@CrispinVV,   Could you supply us with a screen shot showing exactly what URL you are navigating to and what you are clicking? Also, please check the Cloudera Manager log for exceptions.  They might help us understand what is happening. Usually, the log is /var/log/cloudera-scm-server/cloudera-scm-server.log   Lastly, what version of Cloudera Manager are you using? From the Support Menu on the top right of CM, click "About" to see the version.   Thanks! ... View more

@ivten,   The "recommended" my.cnf in the Cloudera documentation is intended, in general, as a suggestion for MySQL used by any role.  DBAs may adjust as needed or desired.   ... View more

@szamasz,   Your observations are correct and expected.  The configuration differences are due to the logic used in Cloudera Manager's management of client configurations. Depending on what roles you have installed on each host, CM will determine the configuration files necessary for clients on those hosts.  If you have a YARN role (NodeManager or Resource Manager) running on the same host as the NameNode, you will probably see the same alternative link to conf.cloudera.yarn.   This is because the YARN configuration will contain client files for YARN as well as HDFS.   If you wish, you can go to your YARN service in Cloudera Manager and click on the Instances subtab.  Click Add new Role Instances and add a new role of "Gateway" to the NameNode host.  Then, deploy client configuration. You will then see that the alternatives link will change to /etc/hadoop/conf.cloudera.yarn   Adding the Gateway Role will allow clients (not Services) to read the current client configuration. Servers do not use the client configuration files in /etc.  Rather, they use the configuration files deployed to the /var/run/cloudera-scm-agent/process directory when starting a service via Cloudera Manager.   I don't know if all of this will help you solve your problem since I didn't see what command you tried to run when the problem happened.  If it doesn't help, please describe what the problem is and we'll help you.   Ben ... View more

@ronnie10,   Hello,   Based on your description, it appears the complaint is that when you click on the Cloudera Manager link for the NameNode UI, it uses the "internal" hostname.  This cannot be influenced unless you changed the name of the internal host to match the hostname your browser is using.  Cloudera Manager generates the URL based on the hostname and domain of the hosts on which the roles are running.   I would recommend either adding the internal hostname as an alias (maybe in hosts file) so the external clients know how to resolve to the correct IP.   There are other ways to work around this... for example,  I think using a reverse proxy with URL rewrite rules may work, for instance depending on your host naming scheme would be something that is possible.   A low-tech solution would be to build a list of URLs that use the public host/IP and put them in web page rather than using the URLs generated by CM.     Ben ... View more