[YARN-3850] NM fails to read files from full disks which can lead to container logs being lost and other issues

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.6.1, 2.8.0, 2.7.1, 3.0.0-alpha1
• Component/s: log-aggregation, nodemanager
• Labels: 2.6.1-candidate
• Target Version/s: 2.7.1
• Hadoop Flags: Reviewed
• Assignee: Varun Saxena
• Reporter: Varun Saxena
• Created: 25/Jun/15 21:28
• Updated: 05/Jan/17 22:42
• Resolved: 26/Jun/15 15:50

Description

Container logs can be lost if disk has become full(~90% full).
When application finishes, we upload logs after aggregation by calling AppLogAggregatorImpl#uploadLogsForContainers. But this call in turns checks the eligible directories on call to LocalDirsHandlerService#getLogDirs which in case of disk full would return nothing. So none of the container logs are aggregated and uploaded.
But on application finish, we also call AppLogAggregatorImpl#doAppLogAggregationPostCleanUp(). This deletes the application directory which contains container logs. This is because it calls LocalDirsHandlerService#getLogDirsForCleanup which returns the full disks as well.
So we are left with neither aggregated logs for the app nor the individual container logs for the app.

In addition to this, there are 2 more issues :

1. ContainerLogsUtil#getContainerLogDirs does not consider full disks so NM will fail to serve up logs from full disks from its web interfaces.
2. RecoveredContainerLaunch#locatePidFile also does not consider full disks so it is possible that on container recovery, PID file is not found.