You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Vitaly Brodetskyi (JIRA)" <ji...@apache.org> on 2016/02/15 22:02:18 UTC

[jira] [Updated] (AMBARI-15051) Improvements and fixes for database check

     [ https://issues.apache.org/jira/browse/AMBARI-15051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

> Improvements and fixes for database check
> -----------------------------------------
>
>                 Key: AMBARI-15051
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15051
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent
>    Affects Versions: 2.2.2
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15051.patch
>
>
> – Log outputs to a separate file (this is already an ask from SmartSense)
> – Use ERROR/WARNING/INFO to mark logs that fit the level
> – Either the python script or the system test validation code can parse the log file for ERROR and WARNING logs and post a summary - as Sunitha Velpula suggested.
> – Take in account fact that clusters count could be more then one in service config check



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)