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

Posted to issues@ambari.apache.org by "Madhuvanthi Radhakrishnan (JIRA)" <ji...@apache.org> on 2018/05/14 20:06:00 UTC

[jira] [Resolved] (AMBARI-23644) Handle back end issues related to new Service Config API

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

Madhuvanthi Radhakrishnan resolved AMBARI-23644.
------------------------------------------------
    Resolution: Fixed

> Handle back end issues related to new Service Config API
> --------------------------------------------------------
>
>                 Key: AMBARI-23644
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23644
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Madhuvanthi Radhakrishnan
>            Assignee: Madhuvanthi Radhakrishnan
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Issue 1: With perf merge/optimization. Configurations are sent over to the agent to be cached when certain events occur. One such event is creation of configs for which we have AgentConfigUpdateEvent. This was being triggered in the "updateCluster" code flow but with new APIs we no longer use it. We use a new function called createServiceConfigVerison so need to add the code to trigger the events.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)