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

Posted to issues@ambari.apache.org by "Dmitry Lysnichenko (JIRA)" <ji...@apache.org> on 2016/04/27 11:00:24 UTC

[jira] [Created] (AMBARI-16134) Force running service checks for services before upgrade

Dmitry Lysnichenko created AMBARI-16134:
-------------------------------------------

             Summary: Force running service checks for services before upgrade
                 Key: AMBARI-16134
                 URL: https://issues.apache.org/jira/browse/AMBARI-16134
             Project: Ambari
          Issue Type: Task
            Reporter: Dmitry Lysnichenko
            Assignee: Dmitry Lysnichenko



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
(v6.3.4#6332)