Bulk Operation

YARN-522 Capture launch_container.sh logs to a separate log file

YARN-522 Print enough container-executor logs for troubleshooting container launch failures

YARN-522 When an export var command fails in launch_container.sh, the full container launch should fail

YARN-522 Add container launch related debug information to container logs when a container fails

YARN-522 create a yarn.troubleshooting log for logging app launching problems

YARN-522 add a way for an attempt to report an attempt failure

YARN-522 LinuxContainerExecutor loses info when forwarding ResourceHandlerException

YARN-522 Add tail of stderr to diagnostics if container fails to launch or it container logs are empty

YARN-522 Include command line, localization info and env vars on AM launch failure

YARN-522 Log the command of launching containers

YARN-522 add more diags about app retry limits on AM failures

YARN-522 Improve exception information on AM launch crashes

YARN-522 The diagnostics is always the ExitCodeException stack when the container crashes

YARN-522 Localization failures should be available in container diagnostics

YARN-522 Difficult to diagnose a failed container launch when error due to invalid environment variable

YARN-522 Failures in container launches due to issues like disk failure are difficult to diagnose

YARN-522 In YarnClient, pull AM logs on AM container failure

YARN-522 Container localization failures aren't reported from NM to RM

YARN-522 On container failure, include logs in diagnostics