@mike_bronson7    It looks like you forgot a parameter  host_components  assuming the ambari server is running on node2 and the thrift Server is on node01 and node02   Delete on Node1 curl -iv -u admin:admin -H "X-Requested-By: ambari" -X DELETE "http://node02:8080/api/v1/clusters/HDP/hosts/node01/host_components/SPARK2_THRIFTSERVER"   Delete on Node 2  curl -iv -u admin:admin -H "X-Requested-By: ambari" -X DELETE "http://node02:8080/api/v1/clusters/HDP/hosts/node02/host_components/SPARK2_THRIFTSERVER" HTH ... View more

@samarsimha    The simplest answer I can give you if compatibility!  HDF/HDP/HCP are packaged applications that have undergone rigorous unitary tests are supposed to "work as"  that explains why you cannot upgrade ONLY a component and upgrade minor or Major released go through a battery of test and QA to ensure all the components work properly. In your case Java 7 and 8 are to date the recommended versions the latter being the most preferred.  From the matrix link https://supportmatrix.hortonworks.com/   I filtered out the latest version of HDF and No HDP/HDF product has been certified against Java 11 as of now, that could change in the near future but it won't definitely be with your current version of Nifi  .   So the above could explain your dilemma. Do you have a special use case as to why you want to use Java 11? I am not sure whether Cloudera offers a workaround but if you bought support from Cloudera then you can open a ticket.   Happy hadooping     ... View more

@deekshant  Can you share these 2 files the .out  logs the start process and the .log is the most interesting   /var/log/hadoop/hdfs/hadoop-hdfs-namenode-<host>.log /var/log/hadoop/hdfs/hadoop-hdfs-namenode-<host>.out Please revert   ... View more

@fgarcia  If you posted something in a thread you and the Admin are the only ones who can delete.  Have a look at the attached screenshot as the author I have the option to edit,  You simply delete everything an save a blank  response there is no delete option except for the Admin   Hope that helps please revert  ... View more

@mike_bronson7    In an HA Cluster, the Standby and Active namenodes have shared storage managed by the journal node service. HA relies on a failover scenario to swap from StandBy to Active Namenode and as any other system in Hadoop it uses zookeepers. So first thing 3 Zookeepers 3 MUST be online to avoid split-brain-decision, below are the steps to follow On the Active Namenode Run the cat commande against the last-promised-epoch in the same directory as edits_inprogress_000.... # cat last-promised-epoch 31 [example output] On the standby Namenode # cat last-promised-epoch 23 [example output] From the above, you will see that the standby had a lag when the power went off. In your case, you should overwrite the one lagging on the standby after backing up as you already did hoping the Namenode has not been put back online if so do a fresh back before you proceed.   SOLUTION Fix the corrupted JN's edits? Instructions to fix that one journal node. 1) Put both NN in safemode ( NN HA) $ hdfs dfsadmin -safemode enter -------output------ Safe mode is ON in Namenode1:8020 Safe mode is ON in Namenode2:8020 2) Save Namespace $ hdfs dfsadmin -saveNamespace -------output------ Save namespace successful for Namenode1:8020 Save namespace successful for Namenode2:8020 3) zip / tar the journal dir from a working JN node and copy it to the non-working JN node to failed node in the same path as the active make sure the file permissions are correct /hadoop/hdfs/journal/<cluster_name>/current 4) Restart HDFS In your case you can start only one Namenode first it will be designated  automatically as the active namenode, once it up and running that is fine, the NameNode failover should now occur transparently and the below alerts should gradually disappear   Stop and restart the journal nodes This will trigger the syncing of the journalnodes, If you wait for a while you should see your Namenodes up and running all "green" # su -l hdfs -c "/usr/hdp/current/hadoop-hdfs-journalnode/../hadoop/sbin/hadoop-daemon.sh stop journalnode" # su -l hdfs -c "/usr/hdp/current/hadoop-hdfs-journalnode/../hadoop/sbin/hadoop-daemon.sh start journalnode"   Start the  standby name node   After a while, things should be in order   Please let me know ... View more

@mike_bronson7  Guess what the copies on the working node should do ! remember files on both nodes directories are identical in an HA setup 🙂  Cheers ... View more

@mike_bronson7    Yeah, but once you bootstrap the zookeeper election will kick in and one will become the active namenode.   It's late here I need to document the process though  I have uploaded it once in HCC, I need to redact  some information, I could do that tomorrow meanwhile can you backup on both the dead and working namenode the following directory zip all content and copy it to some safe directory    /hadoop/hdfs/journal/<Ckuster_name>/current   Please revert ... View more