For each container being activated, the slider agent knows the log
location. If the component instance (within the container) fails to
activate properly or goes down then the user may need access to the log
locations for debugging. *This assumes that appropriate yarn config is in
place to have the
On May 13, 2014, at 3:58 PM, Sumit Mohanty wrote:
> For each container being activated, the slider agent knows the log
> location. If the component instance (within the container) fails to
> activate properly or goes down then the user may need access to the log
> locations for debugging. *This
Makes sense to add the component name.
{conatiner_id: {
*"componentname":"name of the component",*
"hostname":"name of the host",
"agent_log": "folder path to agent log",
"app_log": "folder path to app log" }}
These are local paths on the host and hence are transient. We can also
On May 13, 2014, at 4:43 PM, Sumit Mohanty wrote:
> Makes sense to add the component name.
>
> {conatiner_id: {
>*"componentname":"name of the component",*
>"hostname":"name of the host",
>"agent_log": "folder path to agent log",
>"app_log": "folder path to app log" }}
>
> Thes
On May 13, 2014, at 5:17 PM, Jon Maron wrote:
>
> On May 13, 2014, at 4:43 PM, Sumit Mohanty wrote:
>
>> Makes sense to add the component name.
>>
>> {conatiner_id: {
>> *"componentname":"name of the component",*
>> "hostname":"name of the host",
>> "agent_log": "folder path to agent l
