ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumit Mohanty <smoha...@hortonworks.com>
Subject Re: Ambari Service Configuration file Design
Date Thu, 19 Jun 2014 06:13:23 GMT
inline ...


On Wed, Jun 18, 2014 at 10:48 PM, 赵全超 <zhaoqc@ondemand.cn> wrote:

> There are some questions about Service Configuration:
>
> 1.      In Ambari Design,Service Configuration files eg,core-site.xml are
> not belonging to the service,but belonging to cluster,why ?
>
Its easier to manage a single active version of config for the whole
cluster or per host/host-group. Some of the config files are also shared
across services - as in multiple service types may refer to the same file.
Do you have scenarios where different services need different values for
the same config type?

>
> 2.      Ambari does not support non-XML configuration file types,so put
> these properties into global.xml,However, in global file,there are some
> properties from service config file. Are there rules that which
> configuration property should put in global file?
>
In general, global config type contains properties that cannot be
associated with site xml files (or yaml files that are supported now as
well). So you will find configurations for env.sh files, log/pid
directories, custom users, etc. in the global config. What sort of config
you have in mind?

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message