[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hurley updated AMBARI-18591: ------------------------------------- Attachment: AMBARI-18591.patch > Hive Rolling Upgrade Is No Longer Supported In Ambari > ----------------------------------------------------- > > Key: AMBARI-18591 > URL: https://issues.apache.org/jira/browse/AMBARI-18591 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.5.0 > Reporter: Jonathan Hurley > Assignee: Jonathan Hurley > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-18591.patch > > > HS2 RU expects all users to be using zookeeper based JDBC URLs. However, few > users are using these new Zookeeper discovery urls and they use the old > format, directly specifying the hostname and port number for the HS2 instance > it connects to. During RU, the HS2 port number changes and users using old > url have an outage. Hive needs to be able to support RU without changing the > port. > Due to too many Hive Client user outages as a result of the RU workflow for > HIve, the decision is to just change RU to bounce the HS2 process, knowing > that there will be down time and causing all active queries to fail. So the > runbook for the HS2 process will look like: > * We will no longer change the Hive port at all during either RU or EU. > * During an RU, we will present a message if Hive is present that indicates > that Hive is not rolling and it will be taken down. > * Run the Hive deregister command to remove the ZK entries for the Hive > Servers > * Hive will be shutdown, without draining, during an RU and a new instance > started up on the same port. > In addition, we need to remove the warnings that were added as part of > AMBARI-17319. -- This message was sent by Atlassian JIRA (v6.3.4#6332)