[
https://issues.apache.org/jira/browse/SLIDER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054486#comment-14054486
]
Gour Saha commented on SLIDER-166:
----------------------------------
A git patch file SLIDER-166.patch has been uploaded to fix this issue.
With this change the {{agent.conf}} attribute is being removed from the
*appConfig.json* files shipped with the slider packages. Hence *agent.ini* will
be supported by default. Appropriate documentation is being provided stating
that users can add an {{agent.conf}} attribute in *appConfig.json* file
pointing to a custom *agent.ini*. This custom *agent.ini* will override the
default values.
> agent.ini should be supported by default
> ----------------------------------------
>
> Key: SLIDER-166
> URL: https://issues.apache.org/jira/browse/SLIDER-166
> Project: Slider
> Issue Type: Bug
> Components: agent-provider
> Affects Versions: Slider 0.40
> Reporter: Sumit Mohanty
> Attachments: SLIDER-166.patch
>
>
> Currently, agent.ini file is explicitly provided by the users when creating
> application instance. The agent.ini file should be created per application
> instance as its possible for slider-agent instances for specific application
> instance to have unique configurations.
> For example, a user may want to debug agents at the level DEBUG for a
> specific application instances while not requiring other applications to also
> run with DEBUG level for agent logs.
> Proposal:
> * Slider will have a default agent.ini that gets automatically uploaded
> * Have folks provide overrides when creating an app
> * AM patches the default using overrides and then drops the .ini somewhere in
> the app instance specific directory (default could be in a well-known place)
> * The patched .ini is then handed off to all agent instances through YARN
> localized file support
--
This message was sent by Atlassian JIRA
(v6.2#6252)
