Jonathan Hurley created AMBARI-20851:
----------------------------------------
Summary: Provide Alert For Component OUT_OF_SYNC Issues
Key: AMBARI-20851
URL: https://issues.apache.org/jira/browse/AMBARI-20851
Project: Ambari
Issue Type: Task
Components: ambari-server
Affects Versions: 2.4.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Priority: Critical
Fix For: 2.5.1
Components can become {{OUT_OF_SYNC}} before and after stack upgrades. As a
result, this can affect the success of future upgrade attempts. It seems wrong
to expose a direct way to alter this state since it's calculated from the
agents.
- The logic currently for reporting component versions is as follows:
-- On an agent's initial heartbeat registration, status commands will report
component versions. Subsequent status commands will not.
-- On any START/STOP/RESTART, the component will report a version
This means that if a host is {{OUT_OF_SYNC}} there are two ways to
automatically fix it (assuming the cluster is properly upgraded)
- Restart the agent on that host
- Restart the components which are {{OUT_OF_SYNC}} on that host
It would be good to notify the cluster administrator that there is a problem
with the reported version of the components.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
