[YARN-8464] Async scheduling thread could be interrupted when there are no NodeManagers in cluster

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 3.2.0, 3.1.1
• Component/s: capacity scheduler
• Target Version/s: 3.1.1
• Assignee: Sunil G
• Reporter: Charan Hebri
• Created: 26/Jun/18 22:47
• Updated: 20/Mar/19 04:22
• Resolved: 27/Jun/18 02:46

Description

Test scenario:
1. Make either yarn.nodemanager.log-dirs/yarn.nodemanager.local-dirs read-only
2. Restart NMs via Ambari, none of them show up in the RM UI as expected
3. Revert back the read-only dirs and restart NMs
4. Include a non-existent dir in either yarn.nodemanager.log-dirs/yarn.nodemanager.local-dirs (1 good existing dir + 1 non-existing dir)
5. Restart NMs via Ambari, all NMs show as RUNNING with a Health Report message as expected
6. Submit a MapReduce sleep job, job goes into ACCEPTED state
7. Job stays in ACCEPTED state forever even though all NMs are running and have available memory

 

Credits to charanh who found this issue.