@Rachel Rui Liu I see your similar post here: https://community.hortonworks.com/questions/110402/issue-when-upgrade-hdf212-to-hdf30.html#answer-111776 ... View more

@Rachel Rui Liu You are getting parsing error: [org.xml.sax.SAXParseException; systemId: file:/var/lib/ambari-server/resources/stacks/HDF/2.0/upgrades/nonrolling-upgrade-2.0.xml; lineNumber: 24; columnNumber: 22; cvc-complex-type.2.4.a: Invalid content was found starting with element 'downgrade-allowed'. One of '{upgrade-path, order}' is expected.] at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:335) Above is basically a parsing error. . So to verify the XML "/var/lib/ambari-server/resources/stacks/HDF/2.0/upgrades/nonrolling-upgrade-2.0.xml" OR "/var/lib/ambari-server/resources/stacks/HDF/2.0/upgrades/nonrolling-upgrade-2.1.xml" please do the following: 1. Open the Online XML Parsing URL: http://www.utilities-online.info/xsdvalidation/#.WVxX39OGPx4 2. Now Paste your XML File "/var/lib/ambari-server/resources/stacks/HDF/2.0/upgrades/nonrolling-upgrade-2.0.xml" OR "/var/lib/ambari-server/resources/stacks/HDF/2.0/upgrades/nonrolling-upgrade-2.1.xml" content there. 3. Ambari validates the amove XML file using the XSD present here: https://github.com/apache/ambari/blob/release-2.5.1/ambari-server/src/main/resources/upgrade-pack.xsd#L420-L424 4. So copy the XSD content and then paste it in the XSD section of the http://www.utilities-online.info/xsdvalidation/#.WVxX39OGPx4 link and then click on "Validate XML against XSD" button and then see the error if your XML is valid or not? Example: Here i am trying to validate "hdf-ambari-mpack-2.1.2.0-10.tar.gz" based XML file 'nonrolling-upgrade*.xml' against Ambari 2.5 XSD. This error may occur when you try to apply old "hdf-ambari-mpack" (i see you are using hdf-ambari-mpack-2.1.2.0-10.tar.gz), Please try the latest mpack "hdf-ambari-mpack-3.0.0.0-453.tar.gz". . http://public-repo-1.hortonworks.com/HDF/centos7/3.x/updates/3.0.0.0/tars/hdf_ambari_mp/hdf-ambari-mpack-3.0.0.0-453.tar.gz https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.0.0/bk_release-notes/content/ch_hdf_relnotes.html . . As you are upgrading from HDF 2.1 ro HDF3.0 so suspecting that you might have not used the correct mpack tar of "hdf-ambari-mpack-3.0.0.0-453.tar.gz" please double check the same and compare the XML difference on your local filesystem to find out if by any chance the "nonrolling-upgrade-2.1.xml" is not from old version. ... View more

@jack jack Surely 8/7 is not right. But i was thinking that When you deleted a host from ambari cluster the host count became 7 , But before deleting the host did you Stop the DataNode running on that host? Else from NameNode perspective the Running DataNodes will be still 8 because that DataNode is still reporting to the NameNode. . Because DataNodes are reports to the NameNode, So you should check the NameNode UI to findout the exact number of DataNode. http://$NAMENODE:50070/dfshealth.html#tab-overview Find the "Live DataNodes" . Ambari simply grabs the LiveDataNode count from the NameNode JMX http://$NAMENODE:50070/jmx?qry=Hadoop:service=NameNode,name=FSNamesystemState . So please check the Deleted Host if the DataNode process is still running there? If yes then stop it. # ps -ef | grep DateNode # echo `cat /var/run/hadoop/hdfs/hadoop-hdfs-datanode.pid` # ps -ef | grep `cat /var/run/hadoop/hdfs/hadoop-hdfs-datanode.pid` ######## If the PID is live and running then kill it. ###### # kill -9 `cat /var/run/hadoop/hdfs/hadoop-hdfs-datanode.pid` . ... View more