Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Why CurrentCapacity exceeds MaximumCapacity?

avatar
Explorer

I've configure queue default capacity to 20 dan maximum-capacity to 30. When I see with command "mapred queue -list", CurrentCapacity can exceeds MaximumCapacity (30) even its can exceeds 100% as seen in picture below.

Please explain me why this happen? Thank you.


2017-09-07-215235.jpg
1 ACCEPTED SOLUTION

avatar

Hi @nur majid,

In mapred queue -list output, default capacity and maximum capacity are with respect to Cluster' resources whereas current capacity is with respect to Queue's resources.

Example -

Assume cluster's resources - 10GB

Default Queue default capacity is 20% of cluster's resources which is 2GB

But default queue can go upto 30% of cluster's resources [maximum capacity] which is 3GB

Current capacity is 101% of Queue's capacity [Remember , queue's capacity is 2GB] , so it will come around 2.02GB which is less than 3GB[maximum capacity].

View solution in original post

2 REPLIES 2

avatar

Hi @nur majid,

In mapred queue -list output, default capacity and maximum capacity are with respect to Cluster' resources whereas current capacity is with respect to Queue's resources.

Example -

Assume cluster's resources - 10GB

Default Queue default capacity is 20% of cluster's resources which is 2GB

But default queue can go upto 30% of cluster's resources [maximum capacity] which is 3GB

Current capacity is 101% of Queue's capacity [Remember , queue's capacity is 2GB] , so it will come around 2.02GB which is less than 3GB[maximum capacity].

avatar
Explorer

Well explained @ssathish. I accept this as correct answer. Thank you.