ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jayush Luniya (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8225) Configuration Monitor - Ability to indicate if the configurations have been changed manually outside Ambari
Date Wed, 18 Mar 2015 05:38:38 GMT

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

Jayush Luniya updated AMBARI-8225:
----------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.1.0

> Configuration Monitor - Ability to indicate if the configurations have been changed manually
outside Ambari
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-8225
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8225
>             Project: Ambari
>          Issue Type: Improvement
>            Reporter: Newton Alex
>            Assignee: Newton Alex
>             Fix For: 2.1.0
>
>         Attachments: AmbariConfigurationMonitor-ProposalAndDesign.pdf
>
>
> Users who are familiar with Hadoop configurations (or any other service) tend to change
the configuration files directly on the cluster nodes without using Ambari. It is quicker
and convenient for them to just directly change the files and restart the service on a particular
node rather than going through Ambari.  The downside of this is that Ambari doesn’t recognize
these changes and overwrites them during cluster upgrades or while reconfiguring services.

> Ambari should not be preventing the users from making changes themselves, as it would
be too restrictive. On the other hand, it would greatly benefit Ambari, if it is aware of
the manual configuration changes on the nodes as it can then alert the users of the changes
before doing any of its own.



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

Mime
View raw message