ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18631) Incorporate database consistency check into main Ambari process
Date Thu, 20 Oct 2016 21:42:58 GMT


Hadoop QA commented on AMBARI-18631:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Incorporate database consistency check into main Ambari process
> ---------------------------------------------------------------
>                 Key: AMBARI-18631
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>             Fix For: 2.5.0
>         Attachments: AMBARI-18631.patch
> Currently the database consistency check runs as a separate process prior Ambari process.
The database consistency checker load various modules needed for performing the validations.
(e.g. load stack definitions to be able to compare service configs from stack with configs
from db).
> Once database consistency checker completed Ambari server is started. Ambari server beside
others loads the same modules as database consistency checker.
> This double initialisation adds time to the ambari server startup time which could be
reduced if the database consistency check is moved into the ambari server process.
> Moreover the database consistency check may check at the beginning if the database is
empty and perform the checks only if there is data in the database.

This message was sent by Atlassian JIRA

View raw message