ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lysnichenko (JIRA)" <>
Subject [jira] [Updated] (AMBARI-16134) Force running service checks for services before upgrade
Date Wed, 27 Apr 2016 09:01:13 GMT


Dmitry Lysnichenko updated AMBARI-16134:
    Fix Version/s: 2.4.0

> Force running service checks for services before upgrade
> --------------------------------------------------------
>                 Key: AMBARI-16134
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.4.0
>         Attachments: AMBARI-16134.patch
> Just checking for service checks that were run within the last hour does not seem to
be a warranty of anything. For example, user could install cluster, run service checks once,
and then enable security/LDAP/change configuration as required by some pre-upgrade check/whatever,
and still have Health Check passing.
> So the current idea is to check configuration change history and compare config change
timestamps with last time the service check for related service was run.
> Also log to Ambari log timestamps of latest service checks for services, and timestamps
of latest service config changes (INFO level)

This message was sent by Atlassian JIRA

View raw message