Gour Saha created SLIDER-1185:
---------------------------------
Summary: Make Slider applications more debuggable by providing
additional diagnostics from cmd-line like app-logs, log-links, etc.
Key: SLIDER-1185
URL: https://issues.apache.org/jira/browse/SLIDER-1185
Project: Slider
Issue Type: Bug
Components: appmaster, client
Affects Versions: Slider 0.91
Reporter: Gour Saha
Today, the options to debug a failing Slider application are painful. One
option is to traverse several links in RM UI starting from the application link
and going all the way down to the container logs. An app-owner might have
access to a gateway, but still logs might not be available until the app dies
if the cluster is not enabled with rolling log aggregation.
Slider provides capability to create apps with friendly names and hence to a
certain extent hides the YARN application id. It is not difficult to find the
YARN application id, but then app owners are more used to referring their apps
by their well-known names. All interactions from the command line using the
Slider client requires only the app name.
It would be great to provide additional diagnostics like snippets of logs of
application containers (not AM container), absolute links to container logs in
RM UI, additional YARN-level diagnostics (if available), etc. All these
information should be made available from Slider client so that app-owners can
query directly from cmd-line using app names. Consumers of Slider client as an
SDK will be able to call appropriate APIs and get these diagnostic information.
For example, Ambari Slider Views can now show these diagnostics directly in the
Ambari UI, relieving the app owners of the pain to traverse the RM UI.
At a high level, I am thinking of few additional options from the cmd-line like
-
slider diagnostics --name <app-name> --app-logs
slider diagnostics --name <app-name> --log-links
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
