[ https://issues.apache.org/jira/browse/AMBARI-17319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-17319: ------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) > Provide More Warnings and Messages About Hive's Port Change During Upgrade > -------------------------------------------------------------------------- > > Key: AMBARI-17319 > URL: https://issues.apache.org/jira/browse/AMBARI-17319 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-17319.patch > > > After upgrading from HDP 2.2.4.2 to HDP 2.3.2, the > {{hive.server2.thrift.port}} changed from 10000 to 10010. > For users and applications which reference Hive via a direct URL/port > combination instead of a discovery URL, they will no longer be able to > contact Hive. > Due to the timing of the next Ambari release, there is a risk of regression > with any attempt to fix this issue. The best option is to provide a more > wizard-like approach where Ambari can use the upgrade packs to ask questions > pertaining to the upgrade. The results of those questions will be passed > along with the upgrade pack when starting an upgrade so that rudimentary > decision paths can be taken while performing orchestration. *However, this is > out of scope for this release*. > Instead, the following tasks can be chosen to be implemented in part or as a > whole in an attempt to alleviate this issue. > *Recommended* > h5. Task 1 (Simple Messages) > h6. Development effort: 1 day > - A new pre-requisite check will be created which will determine if the > upgrade is rolling and if Hive is installed. If both conditions are met, a > {{WARNING}} will be triggered which will say something similar to: > bq. You have chosen to perform a rolling upgrade and Hive is currently > installed. Hive supports rolling upgrades, but its port will change as a > result of the upgrade. If this is not the desired behavior, then the port can > be changed back to its original value after the upgrade has completed. > - A new message will be added and displayed to the user post-finalization. > bq. The hive server port has changed as a result of this rolling upgrade. If > this port change is not desired, then you can now use Ambari to return hive > to its original port. > h5. Task 2 (Messages To Alter Configurations) > h6. Development effort: 4 days total > - A new pre-requisite check will be created which will determine if the > upgrade is rolling and if Hive is installed. If both conditions are met, a > {{WARNING}} will be triggered which will say something similar to: > bq. You have chosen to perform a rolling upgrade and Hive is currently > installed. Hive supports rolling upgrades, but its port will change as a > result of the upgrade. If this is not the desired behavior, then you can > choose to set the {{ambari.upgrade.hive.rolling}} property to {{false}} in > {{hive-site}} before continuing with this upgrade. When set to {{false}}, > Hive's port will not change during the upgrade, but Hive will incur downtime > while it is restarted during the upgrade. > - The Hive upgrade scripts will change to look for > {{ambari.upgrade.hive.rolling}} and will choose to do a {{stop}} and a > {{start}} instead of a {{deregister}} > - The XML upgrade packs will be changed to look for > {{ambari.upgrade.hive.rolling}} and only change the hive port based on this > property being {{true}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)