[
https://issues.apache.org/jira/browse/AMBARI-18631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15587147#comment-15587147
]
Hadoop QA commented on AMBARI-18631:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12834043/AMBARI-18631.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8913//console
This message is automatically generated.
> 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
(v6.3.4#6332)
