[YARN-1440] Yarn aggregated logs are difficult for external tools to understand

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: log-aggregation logs tfile yarn
• Assignee: Unassigned
• Reporter: ledion bitincka
• Created: 22/Nov/13 20:39
• Updated: 22/Oct/17 21:20

Description

The log aggregation feature in Yarn is awesome! However, the file type and format in which the log files are aggregated into (TFile) should either be much simpler or be made pluggable. The current TFile format forces anyone who wants to see the files to either
a) use the web UI
b) use the CLI tools (yarn logs) or
c) write custom code to read the files

My suggestion would be to simplify the log collection by collecting and writing the raw log files into a directory structure as follows:

/{log-collection-dir}/{app-id}/{container-id}/{log-file-name} 

This way the application developers can (re)use a much wider array of tools to process the logs.

For the readers who are not familiar with logs and their format you can find more info the following two blog posts:
http://hortonworks.com/blog/simplifying-user-logs-management-and-access-in-yarn/
http://blogs.splunk.com/2013/11/18/hadoop-2-0-rant/