Hi,  I am having the same issue on CDP 7.1.6 with Oozie 5.1.0. But the suggested solution does not seem to work anymore.    Setting                 <property>                     <name>oozie.launcher.yarn.app.mapreduce.am.env</name>                     <value>SPARK_HOME=/opt/cloudera/parcels/CDH/lib/spark/</value>                 </property> has no effect.   Is there anything else I can do? Did the setting change?     ... View more

Hi,  you can get the legacy behavior of "create table" by executing     SET hive.create.as.external.legacy=true;     https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/configuring-apache-hive/topics/hive_create_table_default.html   This gives you the old behavior of hive 1.x / 2.x for your tables     ... View more

@Johannes Mayer There can be two approaches 1. To Suppress the alerts (if they are getting cleared quickly), Means increasing the "timeout" and "check interval" of those alerts. 2. Finding the resources that might be causing the issue like looking at the Memory # free -m # top # Logs of individual components like DataNode & NodeManager (When they were not responding) were there any Long GC pause? Looking at the GC log of DataNode/NodeManager can be helpful to know if there were Long GC pauses? # /var/log/messages to see any abnormal behaviour during the time period. # SAR Report (Historical Data Capturing of the OS which includes various statistocs including IO/CPU/Memory ...etc). . . ... View more

Secondary NameNode in hadoop is a specially dedicated node in HDFS cluster whose main function is to take checkpoints of the file system metadata present on namenode. It is not a backup namenode. It just checkpoints namenode’s file system namespace. The Secondary NameNode is a helper to the primary NameNode but not replace for primary namenode. As the NameNode is the single point of failure in HDFS Ref: http://hadooptutorial.info/tag/secondary-namenode-functions/ ... View more