hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7265) Hadoop Server Log Correlation
Date Thu, 08 Feb 2018 20:39:07 GMT

    [ https://issues.apache.org/jira/browse/YARN-7265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357531#comment-16357531

Arun C Murthy commented on YARN-7265:

[~tanping] - Like [~jlowe] suggested, separating this from YARN makes sense. For e.g. Ambari
has "log search", leveraging that would be a better option. Makes sense? Thanks.

> Hadoop Server Log Correlation  
> -------------------------------
>                 Key: YARN-7265
>                 URL: https://issues.apache.org/jira/browse/YARN-7265
>             Project: Hadoop YARN
>          Issue Type: Wish
>          Components: log-aggregation
>            Reporter: Tanping Wang
>            Priority: Major
> Hadoop has many server logs, yarn tasks logs, node manager logs, HDFS logs..   There
are also a lot of different ways can be used to expose the logs, build relationship horizontally
to correlate the logs or search the logs by keyword. There is a need for a default and yet
convenient  logging analytics mechanism in Hadoop itself that at least covers all the server
logs of Hadoop.  This log analytics system can correlate the Hadoop server logs by grouping
them by various dimensions including application ID,  task ID, job ID or node ID etc.   The
raw logs with correlation can be easily accessed by the application developer or cluster administrator
via web page for managing and debugging.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message