Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 09-08-2017 07:14 AM
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.
Created 09-08-2017 06:40 PM
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].
Created 09-08-2017 06:40 PM
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].
Created 09-11-2017 04:21 AM
Well explained @ssathish. I accept this as correct answer. Thank you.