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 854AC200C2F for ; Mon, 6 Mar 2017 15:45:36 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 82459160B81; Mon, 6 Mar 2017 14:45:36 +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 CD51C160B73 for ; Mon, 6 Mar 2017 15:45:35 +0100 (CET) Received: (qmail 33299 invoked by uid 500); 6 Mar 2017 14:45:35 -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 33285 invoked by uid 99); 6 Mar 2017 14:45:35 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Mar 2017 14:45:35 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A68C0C03CB for ; Mon, 6 Mar 2017 14:45:34 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 7fCDYe8fQ-gM for ; Mon, 6 Mar 2017 14:45:34 +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 EFF535F36B for ; Mon, 6 Mar 2017 14:45:33 +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 5B2F8E0419 for ; Mon, 6 Mar 2017 14:45:33 +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 194962416E for ; Mon, 6 Mar 2017 14:45:33 +0000 (UTC) Date: Mon, 6 Mar 2017 14:45:33 +0000 (UTC) From: =?utf-8?Q?Bal=C3=A1zs_Bence_S=C3=A1ri_=28JIRA=29?= To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-20319) Server startup script keeps waiting even if DB consistency has failed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 06 Mar 2017 14:45:36 -0000 Bal=C3=A1zs Bence S=C3=A1ri created AMBARI-20319: ------------------------------------------ Summary: Server startup script keeps waiting even if DB consis= tency has failed Key: AMBARI-20319 URL: https://issues.apache.org/jira/browse/AMBARI-20319 Project: Ambari Issue Type: Bug Components: ambari-server Affects Versions: 3.0.0, 2.5.0 Reporter: Bal=C3=A1zs Bence S=C3=A1ri Assignee: Bal=C3=A1zs Bence S=C3=A1ri Priority: Minor Fix For: 3.0.0, 2.5.0 The current logic of the Ambari server startup script: 1. Wait for java server process PID 2. Java process starts Database check 3. Script waits until UI becomes available or timeout occurs If DB check fails, the script waits some 50 seconds for the UI, before time= out occurs, although it should fail instantly in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)