Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Yarn Application Failed - Out of Memory - Lack of Queue Resources

Highlighted

Yarn Application Failed - Out of Memory - Lack of Queue Resources

New Contributor

hello friends,

We need your help in better understanding of the issue: The yarn application was failed (based on yarn application logs) due to "out of memory" and the application was submitted to 'default' queue (we are using Capacity Scheduler) and the default queue usage was for today as is below:

+------------+----------------------+--------------------+--------------------+---------------+--------------------+--+

| queue | allocatedcontain | pendingcont | capacity allo | usedcapacity | datetime |

+------------+----------------------+--------------------+--------------------+---------------+--------------------+--+

| default | 551 | 525 | 5.0 | 213.84296 | 08:20:18:17:00:01 |

| default | 519 | 525 | 5.0 | 207.2314 | 08:20:18:16:45:01 |

| default | 492 | 525 | 5.0 | 201.65288 | 08:20:18:16:35:01 |

| default | 1356 | 739 | 5.0 | 380.16528 | 08:20:18:16:15:01 |

| default | 543 | 525 | 5.0 | 212.19008 | 08:20:18:16:00:02 |

| default | 633 | 525 | 5.0 | 230.78513 | 08:20:18:15:45:01 |

| default | 527 | 525 | 5.0 | 208.8843 | 08:20:18:15:35:01 |

| default | 571 | 1524 | 5.0 | 220.04132 | 08:20:18:15:15:02 |

| default | 872 | 4082 | 5.0 | 279.75208 | 08:20:18:15:00:02 |

| default | 1454 | 8716 | 5.0 | 400.41324 | 08:20:18:14:45:02 |

| default | 1454 | 18615 | 5.0 | 400.41324 | 08:20:18:14:35:01 |

| default | 1600 | 22973 | 5.0 | 430.57852 | 08:20:18:14:15:01 |

If you see in the above, the default queue was allocated with only 5% cluster resources, and most of the time, queue was demanding (waiting) for containers (as indicated under: Pending Containers column) --> so finally the job was failed and when we looked into the application (yarn logs) we noticed that it was failed for 'out of memory' errors.

Now the confusion for me is:

1. The job failed for 'out of memory' --> due to (it never got it's requested memory (as indicated above, the 'pending containers count never went down) --> it means, the jobs never got their requested memory --> so the job was failed for 'out of memory' (may be when they don't get their requested memory, they must be in stuck (state) but should not be failed right?

2. The job in fact was processing more data and may be actually looking for a bigger container size (the default container size was set to 8GB)

I just wanted to get some clear picture here, hence i am looking for your advice. I greatly appreciate your time and help.

thanks,

hdpadmin