Vitaly Brodetskyi updated AMBARI-18631:
    Attachment: AMBARI-18631.patch

> Incorporate database consistency check into main Ambari process
> ---------------------------------------------------------------
>                 Key: AMBARI-18631
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18631
>             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

Reply via email to