[
https://issues.apache.org/jira/browse/AMBARI-25956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736192#comment-17736192
]
D M Murali Krishna Reddy commented on AMBARI-25956:
---------------------------------------------------
I too have observed this behaviour during rolling, express upgrades. Once the
upgrade is completed I can see only one hiveserver2 running.
On Checking the upgrade logs I can see that during restarting HiveServer2,
deregister is being executed with the target version of upgrade. Due to this
the HiveServer2 which restarts currently is stopping the HiveServer's that have
restarted earlier.
I feel the change done in hive_server_upgrade.py from
https://issues.apache.org/jira/browse/AMBARI-21722 has induced this issue of
deregistering target version instead of source version. As, In few earlier
tickets AMBARI-12195 , AMBARI-12280 It's mentioned that expected behaviour is
deregistering source version.
> [ Rolling upgrade] Hive Server Going down after upgrade
> -------------------------------------------------------
>
> Key: AMBARI-25956
> URL: https://issues.apache.org/jira/browse/AMBARI-25956
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.7.6
> Reporter: Satheesh Akuthota
> Assignee: D M Murali Krishna Reddy
> Priority: Major
>
> Hi Team ,
> STR :
> 1. Install HDP 2.6.5 cluster with Multiple HS2 clients
> 2. Perform Express or Rolling Upgrade to HDP 3.6.5 vesion through ambari
> Expected Result : All the services should be up and running
> Observed Result : one of the HS2 going down
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
