----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/40004/#review105473 -----------------------------------------------------------
Ship it! ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py (lines 198 - 199) <https://reviews.apache.org/r/40004/#comment164094> Is there anything we can do instead of sleeping? Any command we can run to check? ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml (line 125) <https://reviews.apache.org/r/40004/#comment164095> Thank you! - Nate Cole On Nov. 5, 2015, 9:52 p.m., Alejandro Fernandez wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/40004/ > ----------------------------------------------------------- > > (Updated Nov. 5, 2015, 9:52 p.m.) > > > Review request for Ambari, Dmitro Lisnichenko, Jayush Luniya, Nate Cole, and > Swapan Shridhar. > > > Bugs: AMBARI-13755 > https://issues.apache.org/jira/browse/AMBARI-13755 > > > Repository: ambari > > > Description > ------- > > Setup: > > * Express Upgrade on HDP 2.2.6.0 -> HDP 2.3.0.0 > * Services: HDFS + ZK > * Upgrade completes successfully > * Downgrade after reaching Finalize Upgrade > * Downgrade blocked at Namenode restart > > This is happening because the downgrade command to HDFS needs to coincide > with the same command that was used to upgrade it. > HDFS supports two types of upgrades: > 1. -rollingUpgrade started (allows downgrading so that there is no data loss. > Downgrade is either "-rollingUpgrade started" or "-rollingUpgrade downgrade") > 2. -upgrade (only allows rollback, so any data that was added since the > upgrade will be lost. Rollback is done with "-rollback" command). > > Because Express Upgrade will support only these paths, we will use option 1 > for all cases. > HDP 2.1->2.3 (only upgrade) > HDP 2.2->2.3 (both upgrade and downgrade) > HDP 2.2->2.2.* (both upgrade and downgrade) > HDP 2.3->2.3.* (both upgrade and downgrade) > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py > f941164 > > ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode.py > ade2ec4 > > ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/namenode_upgrade.py > c8c057d > > ambari-server/src/main/resources/stacks/HDP/2.1/upgrades/nonrolling-upgrade-2.3.xml > 0f96d03 > > ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.2.xml > 3a518cf > > ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml > d6328dc > > ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.3.xml > 2f807fd > ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 51ccf59 > > Diff: https://reviews.apache.org/r/40004/diff/ > > > Testing > ------- > > Tested in the following scenarios. > HDP 2.1->2.3: > Express Upgrade: setup with and without HA > > HDP 2.2->2.3: > Express Upgrade: setup with and without HA, followed upgrade and then > downgrade. > Rolling Upgrade: setup with HA, followed upgrade and then downgrade. > > > Thanks, > > Alejandro Fernandez > >
