ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <>
Subject [jira] [Commented] (AMBARI-14690) Configurable system resource values for ambari-agent
Date Thu, 21 Jan 2016 17:05:39 GMT


Vinod Kumar Vavilapalli commented on AMBARI-14690:

Apologies, yesterday was a little spotty.

Yes, good to know (2) works for you too.

Regarding the format, there are two parts: structure and field names. Clearly JSON is standard
'enough'. The second one seems better in terms of structure. The names are also part of the
contract though, so we will need to see if we want to borrow the names from /proc/meminfo
or just create our own.

> Configurable system resource values for ambari-agent
> ----------------------------------------------------
>                 Key: AMBARI-14690
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-agent
>    Affects Versions: 2.4.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 2.4.0
>         Attachments: AMBARI-14690.patch
> When an ambari agent starts, host system details are registered into ambari server database.
These values are calculated by ambari-agents based on different files on the hosts (e.g :
> In some cases it isn't a correct behavior: If ambari-agent is in a docker-container,
it will see the same memory/cpu details. (stack advisor also uses these values, its possible
stack advisor can recommend a too high memory value for some services)
> Solution: Configurable system resources in ambari-agent.ini (if a value does not exist
or empty, it will use the default behavior)
> {code:java}
> [system_resource]
> processorcount=2
> physicalprocessorcount=2
> memorysize=50000
> memoryfree=50000
> memorytotal=100000
> swapsize=20
> swapfree=20
> ...
> {code}
> In ambari-agent set these values, all of the factor info values can be redefined
in ambari-agent.ini file.
> That means ambari is not responsible to gather these values from the system.
> - use case: 
> During 'docker run' , if there is a script which calls 'ambari-agent start', before that,
some of the memory values can be replaced/inserted into the ambari-agent.ini file in that
script. (e.g. the user knows that, 4 ambari-agent containers will be started, with the same
services, so the real memory needs to be devided by 4 etc.)
> is called during ambari-agent start, so if the values will be modified later,
ambari-agent needs to be restarted.

This message was sent by Atlassian JIRA

View raw message