On May 13, 2014, at 3:58 PM, Sumit Mohanty <smoha...@hortonworks.com> 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 assumes that appropriate yarn config is in
> place to have the log files hang around for a while.*
>
> What do you think about the capability to have the agent report back these
> information (log locations etc.) and have them published. There needs to be
> a limit on how long the information should be available as number of failed
> containers may grow over time. An obvious limit could be the yarn
> configuration of how long the logs are saved on the host.
>
> Should we publish them as:
>
> {conatiner_id: {
> "hostname":"name of the host",
> "agent_log": "folder path to agent log",
> "app_log": "folder path to app log" }}
- would probably help to add “component:” or “role:” property to ease
correlation with the given component
- are the paths in HDFS or do they reference an exposed endpoint that allows
for the download of the logs (e.g.
http://host:port/ws/v1/slider/diagnostics/someLogName)?
>
> We can add more diagnostics information as needed.
>
> Any suggestion on a good location to publish this?
Perhaps a root resource that lists the information for the cluster is where
you’d start: /ws/v1/slider/diagnostics. Individual entries (with perhaps more
detail) could be retrieved as /ws/v1/slider/diagnostics/container_id (these
hrefs should probably be available as properties in the root resource)
>
> -Sumit
>
> --
> 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.
--
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.
