Hi, I'm trying to understand a little more about what these options do behind the scenes when pressed?  I found this post, but it never got any responses (http://community.cloudera.com/t5/Web-UI-Hue-Beeswax/What-is-under-the-hood-of-Hue-Impala-editor-Clear-cache/m-p/59814#M2432) Clear Cache This is the one I am not too sure what happens Perform Incremental metadata Update I assume this issues a refresh command for all tables within the current database which is been viewed?  If no database is veiwed does it do it for everything? Invalidate All metadata and rebuild index Same as above, but rather than refresh it invalidates full metadata?  If no database is veiwed does it do it for everything? ... View more

Hi, I have a simple oozie workflow which runs an impala-shell and exeutes a impala query file.  The query is a big one so I expect to see if take a few hours, however worlflow keeps getting killed after 1 hour.  When looking through the logs I see on the impala-shell logs the following "timeout 1hr" >>> Invoking Shell command line now >> Stdoutput Generating kerberos ticket, attempt 0, fromxxx.keytab for xxx@xxx.xom Stdoutput Sucessfully obtained Kerberos ticket for xxx@xxx.com Stdoutput Generating random string Stdoutput Query parameters: Stdoutput tempTable=temp._attxxx_60742242 Stdoutput 0: Running query query.sql with timeout 1h, attempt 0, parameters: The impala admission queue the query executes under has no timeout setting set, so i'm at a loss as to were this value is been picked up from? ... View more

Hi, I've just upgraded the cluster from 5.14 to 5.16, however none of the node managers will start.  They give the error: 2018-12-04 13:26:15,283 DEBUG org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor: checkLinuxExecutorSetup: [/var/lib/yarn-ce/bin/container-executor, --checksetup] 2018-12-04 13:26:15,287 WARN org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor: Exit code from container executor initialization is : 24 ExitCodeException exitCode=24: Invalid conf file provided : /var/lib/yarn-ce/etc/hadoop/container-executor.cfg at org.apache.hadoop.util.Shell.runCommand(Shell.java:604) at org.apache.hadoop.util.Shell.run(Shell.java:507) at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:789) at org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor.init(LinuxContainerExecutor.java:193) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.serviceInit(NodeManager.java:267) at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.initAndStartNodeManager(NodeManager.java:562) at org.apache.hadoop.yarn.server.nodemanager.NodeManager.main(NodeManager.java:609) I've read various articles about permissions etc, none of which seem to work.  The file /var/lib/yarn-ce/etc/hadoop/container-executor.cfg seems to be recreated every time I attempt to start the node manager.  I know there was some bug fixes in 5.15 and 5.16 releating to this. Any help would be greatly apprichated as the cluster is currently down. ... View more

Hi, I'm going to be upgrading our CM/CDH 5.14 cluster to 5.16.  I've noticed a new step named "Hue Document cleanup" (https://www.cloudera.com/documentation/enterprise/upgrade/topics/ug_cdh_upgrade.html#cdh_upgrade5) Looking at the estimate given (1 minute per 1000 rows), this would take around 3 hours at best on my cluster (MySQL backend). Can these scripts be run with theh cluster still operational and will if affect anything?  Ideally I would like to run this outside of my maintenance window to save time, but can only do so if the cluster will still be in a usable state. ... View more