Return-Path: X-Original-To: apmail-ambari-issues-archive@minotaur.apache.org Delivered-To: apmail-ambari-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 49BCA19E1B for ; Wed, 27 Apr 2016 21:03:13 +0000 (UTC) Received: (qmail 22299 invoked by uid 500); 27 Apr 2016 21:03:13 -0000 Delivered-To: apmail-ambari-issues-archive@ambari.apache.org Received: (qmail 22243 invoked by uid 500); 27 Apr 2016 21:03:13 -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 22204 invoked by uid 99); 27 Apr 2016 21:03:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2016 21:03:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E231B2C1F54 for ; Wed, 27 Apr 2016 21:03:12 +0000 (UTC) Date: Wed, 27 Apr 2016 21:03:12 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-16094) Improvements to DB consistency check MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-16094?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 260939#comment-15260939 ]=20 Hadoop QA commented on AMBARI-16094: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest a= ttachment=20 http://issues.apache.org/jira/secure/attachment/12801088/AMBARI-16094.pat= ch 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 2 = 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 incre= ase 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.controller.utilities.DatabaseChe= ckerTest Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6692//t= estReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6692/= /console This message is automatically generated. > Improvements to DB consistency check > ------------------------------------ > > Key: AMBARI-16094 > URL: https://issues.apache.org/jira/browse/AMBARI-16094 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.4.0 > Reporter: Vitaly Brodetskyi > Assignee: Vitaly Brodetskyi > Priority: Critical > Fix For: 2.4.0 > > Attachments: AMBARI-16094.patch > > > * disable (we can remove later) DatabaseCheck > * Have CheckDatabaseHelper be called as part of ambari-server start > ** Modify {{ambari-server start}} to so that it calls {{ambari-server che= ck-database}} > *ambari-server check-database improvements* > * On the output modify {{Ambari Server 'check-database' completed success= fully.}} to {{Ambari Server 'check-database' completed.}} - _remove success= fully_ > * Use =E2=80=9C--skip-database-check=E2=80=9D (not skip-database-validati= on) to force ambari-server to start despite error > * If there is error when check-database is run then use the following tex= t > {code} > DB configs consistency check failed. Run =E2=80=9Cambari-server start --s= kip-database-check=E2=80=9D to skip. If you use this =E2=80=9C--skip-databa= se-check=E2=80=9D option, do not make any changes to your cluster topology = or perform a cluster upgrade until you correct the database consistency iss= ues. See "/var/log/ambari-server/ambari-check-database.log" for more detail= s on the consistency issues. > {code} > *ambari-server start improvements* > * On Ambari Server start, the output failure text to should mention ambar= i-server.log (in addition to .out file it does today) > * If user has not specified {{--skip-database-check}} fail start command = if check-database reports error > * When user starts server with --skip-database-check, if there are DB che= ck errors, print message: > {code} > Ambari Server is starting with the database consistency check skipped. Do= not make any changes to your cluster topology or perform a cluster upgrade= until you correct the database consistency issues. See "/var/log/ambari-se= rver/ambari-check-database.log" for more details on the consistency issues. > {code} > When using log file paths, make sure to use the right path from log4j. > *Optional* > Modify ambari.properties to add {{database_check_error_skipped=3Dtrue}} i= f user started with {{--skip-database-check}} and there were errors due to = database-check. If there are no errors then store {{database_check_error_sk= ipped=3Dfalse}}. Eventually, UI will use this property and show warnings to= the user and even prevent HDP upgrade or other topology modifying operatio= ns such as Add Host/Service. -- This message was sent by Atlassian JIRA (v6.3.4#6332)