capacity-scheduler.xml.template 2.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. <?xml version="1.0"?>
  2. <!-- This is the configuration file for the resource manager in Hadoop. -->
  3. <!-- You can configure various scheduling parameters related to queues. -->
  4. <!-- The properties for a queue follow a naming convention,such as, -->
  5. <!-- mapred.capacity-scheduler.queue.<queue-name>.property-name. -->
  6. <configuration>
  7. <property>
  8. <name>mapred.capacity-scheduler.queue.default.guaranteed-capacity</name>
  9. <value>100</value>
  10. <description>Percentage of the number of slots in the cluster that are
  11. guaranteed to be available for jobs in this queue.
  12. </description>
  13. </property>
  14. <property>
  15. <name>mapred.capacity-scheduler.queue.default.reclaim-time-limit</name>
  16. <value>300</value>
  17. <description>The amount of time, in seconds, before which
  18. resources distributed to other queues will be reclaimed.
  19. </description>
  20. </property>
  21. <property>
  22. <name>mapred.capacity-scheduler.queue.default.supports-priority</name>
  23. <value>false</value>
  24. <description>If true, priorities of jobs will be taken into
  25. account in scheduling decisions.
  26. </description>
  27. </property>
  28. <property>
  29. <name>mapred.capacity-scheduler.queue.default.minimum-user-limit-percent</name>
  30. <value>100</value>
  31. <description> Each queue enforces a limit on the percentage of resources
  32. allocated to a user at any given time, if there is competition for them.
  33. This user limit can vary between a minimum and maximum value. The former
  34. depends on the number of users who have submitted jobs, and the latter is
  35. set to this property value. For example, suppose the value of this
  36. property is 25. If two users have submitted jobs to a queue, no single
  37. user can use more than 50% of the queue resources. If a third user submits
  38. a job, no single user can use more than 33% of the queue resources. With 4
  39. or more users, no user can use more than 25% of the queue's resources. A
  40. value of 100 implies no user limits are imposed.
  41. </description>
  42. </property>
  43. </configuration>