Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AB941200C53 for ; Tue, 28 Mar 2017 04:09:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AA285160B9A; Tue, 28 Mar 2017 02:09:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ED7CC160B85 for ; Tue, 28 Mar 2017 04:09:44 +0200 (CEST) Received: (qmail 61173 invoked by uid 500); 28 Mar 2017 02:09:44 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 61164 invoked by uid 99); 28 Mar 2017 02:09:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 02:09:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A4C421A57B3 for ; Tue, 28 Mar 2017 02:09:43 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id uaKnLcgqhAyL for ; Tue, 28 Mar 2017 02:09:42 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 99D485FB7A for ; Tue, 28 Mar 2017 02:09:42 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DD774E0596 for ; Tue, 28 Mar 2017 02:09:41 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9554824065 for ; Tue, 28 Mar 2017 02:09:41 +0000 (UTC) Date: Tue, 28 Mar 2017 02:09:41 +0000 (UTC) From: "Sviatoslav Tereshchenko (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-20593) EU/RU Auto-Retry does not reschedule task when host is not heartbeating before task is scheduled and doesn't have a start time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Mar 2017 02:09:45 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944406#comment-15944406 ] Sviatoslav Tereshchenko commented on AMBARI-20593: -------------------------------------------------- fyi [~afernandez] > EU/RU Auto-Retry does not reschedule task when host is not heartbeating before task is scheduled and doesn't have a start time > ------------------------------------------------------------------------------------------------------------------------------ > > Key: AMBARI-20593 > URL: https://issues.apache.org/jira/browse/AMBARI-20593 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.5.0 > Environment: rolling upgrade > Reporter: Sviatoslav Tereshchenko > Assignee: Alejandro Fernandez > Labels: rolling_upgrade > Fix For: 2.5.1 > > > STR: > 1) Install ambari 2.5.0.1 > In the ambari.properties file, set > stack.upgrade.auto.retry.timeout.mins=6 > stack.upgrade.auto.retry.check.interval.secs=30 > 2) Install HDP with any set of services > 3) Add NameNode HA > 4) Register and install new HDP stack version > 5) Start RU > 5) Corrupt one step from Core Masters group (e.g., stop ambari-agent on a node while the command is running) > Ambari will restart Restarting NN Batch 1 > 6) Fix corrupted step (e.g., start ambari-agent again) > 7) Corrupt another step from before the command is scheduled (e.g., stop ambari-agent on a node) > 8) Fix corrupted step (e.g., start ambari-agent agent) > The expectation is that Ambari Server should schedule the command on the 2nd node. However, because the command never got an original_start_time and start_time, the RetryUpgradeActionService was not able to retry it since it didn't have any timestamps to compare against. -- This message was sent by Atlassian JIRA (v6.3.15#6346)