[jira] [Commented] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575462#comment-15575462 ] Hudson commented on AMBARI-18591: - SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #147 (See [https://builds.apache.org/job/Ambari-branch-2.5/147/]) AMBARI-18591 - Hive Rolling Upgrade Is No Longer Supported In Ambari (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=4ae5b834d384356ac4dd061c97892ab918cb1abf]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (delete) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarningTest.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveNotRollingWarningTest.java * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveNotRollingWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarning.java > 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)
[jira] [Commented] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[ https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15575436#comment-15575436 ] Hudson commented on AMBARI-18591: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #5800 (See [https://builds.apache.org/job/Ambari-trunk-Commit/5800/]) AMBARI-18591 - Hive Rolling Upgrade Is No Longer Supported In Ambari (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=9b0f631765f1e1c5855b95943c5cfb8c9cfff879]) * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.2.xml * (add) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveNotRollingWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/main/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarning.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/upgrade-2.5.xml * (delete) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveRollingPortChangeWarningTest.java * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/upgrade-2.3.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.4.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server.py * (edit) ambari-server/src/test/python/stacks/2.0.6/HIVE/test_hive_server.py * (edit) ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/upgrade-2.5.xml * (edit) ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml * (edit) ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/package/scripts/hive_server_upgrade.py * (add) ambari-server/src/test/java/org/apache/ambari/server/checks/HiveNotRollingWarningTest.java > 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)
[jira] [Commented] (AMBARI-18591) Hive Rolling Upgrade Is No Longer Supported In Ambari
[
https://issues.apache.org/jira/browse/AMBARI-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15572817#comment-15572817
]
Hadoop QA commented on AMBARI-18591:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12833160/AMBARI-18591.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.cluster.ClustersDeadlockTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8870//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8870//console
This message is automatically generated.
> 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)
