You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/11/15 02:39:34 UTC
[jira] [Updated] (AMBARI-6286) Get rid of using macros as
enviroment variables for nagios
[ https://issues.apache.org/jira/browse/AMBARI-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yusaku Sako updated AMBARI-6286:
--------------------------------
Fix Version/s: (was: 1.7.0)
2.0.0
> Get rid of using macros as enviroment variables for nagios
> ----------------------------------------------------------
>
> Key: AMBARI-6286
> URL: https://issues.apache.org/jira/browse/AMBARI-6286
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.0.0
>
>
> Macros are normally made available to check, notification, event handler, etc. commands as environment variables.
> This can be a problem in a large Nagios installation, as it consumes some additional memory and (more importantly) more CPU.
> If your scripts don't need to access the macros as environment variables (e.g. you pass all necessary macros on the command line), you don't need this feature.
> You can prevent macros from being made available as environment variables by using the enable_environment_macros option.
>
> we have 3 enviroment macros used in check_wrapper.sh, and some in other
> scripts, we can excplicetely set them to env by editting hadoop-commands.cfg
> Benefit: we can stop using expensive enable_environment_macros, and have
> alerts working on large cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)