ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13801) Upgrade Pre-Req Check Is Confusing When Hosts Are In Maintenance Mode
Date Tue, 10 Nov 2015 01:48:11 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997827#comment-14997827
] 

Hudson commented on AMBARI-13801:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #3797 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3797/])
AMBARI-13801 - Upgrade Pre-Req Check Is Confusing When Hosts Are In (jhurley: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c715189ab50311f5fc2ed0b089e426173b59fd25])
* ambari-server/src/main/java/org/apache/ambari/server/checks/HostsHeartbeatCheck.java
* ambari-server/src/main/java/org/apache/ambari/server/state/stack/PrerequisiteCheck.java
* ambari-server/src/main/java/org/apache/ambari/server/checks/CheckDescription.java
* ambari-server/src/main/java/org/apache/ambari/server/checks/HostMaintenanceModeCheck.java
* ambari-server/src/test/java/org/apache/ambari/server/checks/HostsHeartbeatCheckTest.java
* ambari-server/src/test/java/org/apache/ambari/server/checks/HostMaintenanceModeCheckTest.java


> Upgrade Pre-Req Check Is Confusing When Hosts Are In Maintenance Mode
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-13801
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13801
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.3
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13801.patch
>
>
> During Upgrade Pre-Req Check, when there are hosts in maintenance mode, a confusing messaging
is shown where the title says “All hosts should be heartbeating” but the warning message
says “Following hosts are in Maintenance Mode”. These checks should be broken into two
distinct checks: one for heartbeating, one for hosts in maintenance mode.
> Currently, we only have 1 check for this. It will produce a {{FAIL}} if there are hosts
not heartbeating and not in MM and will produce an {{WARNING}} if there are hosts in MM. We
can separate these out into two distinct checks. In which case:
> - The hosts heartbeating check would only report a {{FAIL}} and _not_ a {{WARNING}}
> - The hosts in MM check would only report a {{WARNING}}, never a {{FAIL}}
> - The heartbeat check would always be performed before the MM check
> {panel:title=Heartbeating}
> Description: All hosts must be communicating with Ambari. Hosts which are not reachable
should be placed in Maintenance Mode.
> Failure Reason: There are hosts which are not communicating with Ambari.
> Hosts: c6401.ambari.apache.org
> {panel}
> {panel:title=MM Check}
> Description: Hosts in maintenance mode will be excluded from the upgrade.
> Warning Reason: There are hosts in maintenance mode which will be excluded from the upgrade.
> Hosts: c6402.ambari.apache.org
> {panel}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message