ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-8225) Configuration Monitor - Ability to indicate if the configurations have been changed manually outside Ambari
Date Sat, 08 Nov 2014 14:44:34 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203453#comment-14203453
] 

Jeff Sposetti commented on AMBARI-8225:
---------------------------------------

Thanks [~nalex]. This is a great start! A few things:

1) When showing sync status on the services summary area, if a subset of hosts are out of
sync, what will it display? Think a red icon with "X of Y hosts out of sync" 
2) I think that text would link to hosts page so users can find the out of sync hosts
3) Would need to think about how this is shown and filtered per host on the Hosts page so
a user can find host(s) that have out of sync config status
4) And on the Host details page, show sync icon info with each component (i.e. my DataNode
component might be out of sync but not the NodeManager on a given host)
5) Also will need a phase 3: on save config, if configs are out of sync, how will the flow
go. Should prompt user to proceed + overwrite or merge?

> 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.0.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