Jonathan Hurley created AMBARI-12264:
----------------------------------------

             Summary: Some Execution Commands Send Stale Configs During Upgrade 
Causing Invalid Alerts
                 Key: AMBARI-12264
                 URL: https://issues.apache.org/jira/browse/AMBARI-12264
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.1.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Blocker
             Fix For: 2.1.0


During an upgrade, the alert check for hive transitions to the new port, 
{{10010}} and begins returning valid checks once the upgraded hive server 
starts up on the new port. 

However, after the upgrade is finalized, it is observed that the configurations 
sent down to the agents contains the old hive thrift port, {{10000}} from 
before the upgrade ran. 

Restarting the agents corrects the problems since the configurations in ambari 
server are still correct.

The problem is that some commands, namely, {{ACTIONEXECUTE}} must also set
- {code}
    "forceRefreshConfigTagsBeforeExecution": [
        "*"
    ],
{code}

on the {{ExecutionCommands}} being sent down.



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

Reply via email to