Bulk Operation

YARN-431 Log aggregation finish time should get logged for trouble shooting.

YARN-431 Node's Log Aggregation Report with SUCCEED should not cached in RMApps

YARN-431 Improve YARN log command to get AMContainer logs as well as running containers logs

YARN-431 IOException in AppLogAggregatorImpl does not give stacktrace and leaves aggregated TFile in a bad state.

YARN-431 Enhance yarn logs command to specify the filename to be retrieved

YARN-431 Enhance yarn logs CLI to allow logs to be pulled for a given containerId without specifying nodeAddress

YARN-431 Yarn aggregated logs are difficult for external tools to understand

YARN-431 Related Web UI, CLI changes on exposing client API to check log aggregation status

YARN-431 NM need to notify the log aggregation status to RM through Node heartbeat

YARN-431 Expose a client API to allow clients to figure if log aggregation is complete

YARN-431 $yarn logs command should return an appropriate error message if YARN application is still running

YARN-431 NM containerlogs servlet can't handle logs of more than a GB

YARN-431 Ability to limit or avoid aggregating logs beyond a certain size

YARN-431 Make container logs available over HTTP in plain text

YARN-431 Documentation for Log Aggregation and log retrieval.

YARN-431 Log aggregation should not assume an AppMaster will have containerId 1

YARN-431 NM should provide a way for AM to tell it not to aggregate logs.

YARN-431 NM should limit number of applications who's logs are being aggregated

YARN-431 NM should aggregate logs when application finishes.

YARN-431 Log Aggregation generates a storm of fsync() for namenode

YARN-431 yarn log does not output all needed information, and is in a binary format

YARN-431 Page navigation support for container logs page and the logs web-service on NMs

YARN-431 NodeManager should serve logs directly if log-aggregation is not enabled

YARN-431 nodemanager log aggregation has scaling issues with namenode

YARN-431 Allow per job log aggregation configuration