@Michael Bronson If you are not using Spark2 currently then you should remove the Spark Service prior to starting the HDP upgrade. (one the upgrade is done then you can install it back) During the upgrade it is not recommended to Add / Remove any service as it can cause severe DB inconsistency. . Following link talks about the Prerequisite of HDP upgrade: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/upgrading_HDP_prerequisites.html Following are the snippet from the above link: Service Maintenance Mode No Services can be in Maintenance Mode. Services Started All Services must be started. . ... View more

@Michael Bronson Both are correct (Supportmatrix and the Docs) 1. Supportmatrix is correct. Means you can run HDP 2.6.5 with Ambari 2.6.1/ 2.6.1.5 /2.6.2.0 / 2.6.2.2 2. The doc is also correct as it talks about a Best Recommendation: It is strongly recommended that you first upgrade to Ambari 2.6.2 before upgrading HDP unless otherwise noted. Ambari 2.6.2 supports patch and maintenance upgrades to HDP 2.6.5.x stack. If i will have to run HDP 2.6.5 then i will also go for latest ambari which supports HDP 2.6.5 (means Ambari 2.6.2.2). This is because with Ambari 2.6.2 we get patch and maintenance upgrades to HDP 2.6.5.x stack. https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-upgrade-ppc/content/performing_a_patch_upgrade.html Patch upgrade is supported only for clusters running HDP-2.6.4 and above. So if you are running Ambari 2.6.1 (with HDP 2.6.5) then you will be laking a major feature of Ambari which can help you in performing patch upgrade. Thats the reason it is recommended to upgrade to Ambari 2.6.2 (ot better Ambari 2.6.2.2). ... View more

@Michael Bronson :: we want to upgrade to the latest HDP 3.1 and latest ambari 2.7.2 >>> Ambari 2.7.3 is better option and more recommended then Ambari 2.7.2. So if you are planning to upgrade Ambari then please go for Ambari 2.7.3 (instead of 2.7.2) The Steps will be as following: 1. Upgrade Ambari-2.6.x to Ambari-2.7.3. 2. Then, use Ambari-2.7.3 to upgrade HDP-2.6.x to HDP-3.1.0. Query: is it safe to jump from old HDP and ambari version to the latest ? Yes, As per upgrade path you can upgrade from Ambari 2.6.1 to Ambari 2.7.3 Query: dose hortonwoks tested this scenario ? ( upgrade HDP 2.6.4 to HDP 3.1 ) Ambari 2.7.3 only supports fully managing a HDP 3.1.x cluster. Not all cluster management operations are supported when using Ambari 2.7.3 with HDP 2.6. Which means once the Ambari Upgrade to 2.7.3 is is best to start upgrading HDP to 3.1. So you should plan accordingly. While you are planning to upgrade to Ambari 2.7.3 (from Ambari 2.6) then please also make a note to take a Ambari DB dump before the ambari upgrade and also go through the Supported DB versions from the following link. As you might also have to upgrade the Database. DB related. For example Ambari 2.6.1 supports Postgres 9.4 / 9.3 / 9.1.13+. MySQL 5.6 Maria DB 10.1. ...etc But Ambari 2.7.3 is tested and certified with Postgres 10.5/ 10.2 / 9.6 and MySQL 5.7 and MariaDB 10.2 ....etc https://supportmatrix.hortonworks.com/ Also during the Ambari upgrade following will be removed: Please refer to : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/bk_ambari-upgrade-major/content/bhvr_changes_upgrade_hdp3_amb27.html The Ambari 2.6.x to Ambari 2.7.3 (HDP 3.1) upgrade will remove the following views: Hive View 1.5, Hive View 2 Hue To Ambari View Migration Slider Storm Tez Pig Rest of the step by step instructions can be found in the following Doc: https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/bk_ambari-upgrade-major/content/ambari_upgrade_guide.html It will be also good to go through the Ambari Release Notes specially the "Behaviour Change" & "New Features" of Ambari 2.7.0 / 2.7.1 / 2.7.3 before the upgrade so that you will be aware of some of the changes. For example in case of Kerberos Environment you should have the kadmin/ principal existing in your KDC server already (or you will have to create one) as described in: https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/bk_ambari-upgrade-major-ppc/content/upgrading_HDP_prerequisites.html https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-release-notes/content/ch_relnotes-ambari-2.7.0.0.html https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.1.0/bk_ambari-release-notes/content/ch_relnotes-ambari-2.7.1.0.html https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.3.0/ambari-release-notes/content/ambari_relnotes.html ... View more

@Michael Bronson Following doc explains step by step instruction to perform this activity (including taking various backups) https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/ambari_upgrade_guide.html Getting Ready: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/preparing_to_upgrade_ambari_and_hdp.html Basically you will need to first upgrade Ambari and then perform the HDP upgrade. Upgrading Ambari to 2.6.2.2: (also the ambari Post upgrade steps) https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/preparing_to_upgrade_ambari_and_hdp.html Upgrading HDP to HDP 2.6.5: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-upgrade/content/upgrading_hdp_stack.html ... View more

@Vishwa Golakoti As we see: raise Fail("Failed to execute nifi cli.sh command") . By any chance are you running Ambari Agent as a Non Root user on the Nifi Host? If yes then can you please check if you have given the Sudoer permission the following file properly isnide your "/etc/sudoer" file for that user? "/var/lib/ambari-agent/tmp/nifi-toolkit-x.x.x.x.x/bin/cli.sh *" If above is not the case then can you please provide the following info and test the following: 1. What is your exact HDF version which you are using ? 2. Can you please check and share the output of the following command from NiFi host where the startup is failing? # grep 'stack_support_nifi_auto_client_registration' /var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/nifi.py Just in case if you see the output as following: Original Lines # grep 'stack_support_nifi_auto_client_registration' /var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/nifi.py if params.nifi_registry_url and params.stack_support_nifi_auto_client_registration: Changed Line # grep 'stack_support_nifi_auto_client_registration' /var/lib/ambari-agent/cache/common-services/NIFI/1.0.0/package/scripts/nifi.py if params.nifi_registry_url and params.stack_support_nifi_auto_client_registration and False: Then for a quick test can you change that line by appending " and False:" at the end like following and then restart NiFi again from ambari UI? The above change will skip the NiFi's client registration on startup and might prevent NiFi Startup failure. In Later version of HDF that script is already changed as following to include the "force_skip_registry_registration":     if params.nifi_registry_url and params.stack_support_nifi_auto_client_registration and not params.force_skip_registry_registration: . . ... View more