Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 4 May 2016 12:01:13 +0000 (UTC)
From: "Hadoop QA (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12962273.1461597384000.107472.1462363273011@Atlassian.JIRA>
In-Reply-To: <JIRA.12962273.1461597384000@Atlassian.JIRA>
References: <JIRA.12962273.1461597384000@Atlassian.JIRA> <JIRA.12962273.1461597384402@arcas>
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
archived-at: Wed, 04 May 2016 12:01:15 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-16094?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
270521#comment-15270521 ]=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/12802150/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 3 =
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.internal.HostResource=
ProviderTest

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/6775//t=
estReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6775/=
/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)