Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Sat, 8 Nov 2014 14:44:34 +0000 (UTC)
From: "Jeff Sposetti (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12753874.1415409041000.453194.1415457874308@Atlassian.JIRA>
In-Reply-To: <JIRA.12753874.1415409041000@Atlassian.JIRA>
References: <JIRA.12753874.1415409041000@Atlassian.JIRA>
 <JIRA.12753874.1415409041341@arcas>
Subject: [jira] [Commented] (AMBARI-8225) Configuration Monitor - Ability to
 indicate if the configurations have been changed manually outside Ambari
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/AMBARI-8225?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D142=
03453#comment-14203453 ]=20

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 ho=
sts are out of sync, what will it display? Think a red icon with "X of Y ho=
sts out of sync"=20
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, ho=
w will the flow go. Should prompt user to proceed + overwrite or merge?

> Configuration Monitor - Ability to indicate if the configurations have be=
en 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 withou=
t using Ambari. It is quicker and convenient for them to just directly chan=
ge the files and restart the service on a particular node rather than going=
 through Ambari.  The downside of this is that Ambari doesn=E2=80=99t recog=
nize these changes and overwrites them during cluster upgrades or while rec=
onfiguring services.=20
> Ambari should not be preventing the users from making changes themselves,=
 as it would be too restrictive. On the other hand, it would greatly benefi=
t Ambari, if it is aware of the manual configuration changes on the nodes a=
s 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)