Manage Work Queue Capacity
Work queues are used to allocate cluster resources among users. When you create a job you specify the work queue to be used when the job is executed.
Oracle Big Data Cloud uses the YARN capacity scheduler for work queues. A set of work queues is created by default when a cluster is created. Which queues get created is determined by the queue profile specified when the cluster was created and whether preemption was set to Off or On. The preemption setting can't be changed after a cluster is created.
-
dedicated: Queue used for all REST API and Zeppelin job submissions. Default capacity is 80, with a maximum capacity of 80.
-
default: Queue used for all Hive and Spark Thrift job submissions. Default capacity is 20, with a maximum capacity of 20.
-
api: Queue used for all REST API job submissions. Default capacity is 50, with a maximum capacity of 100.
-
interactive: Queue used for all Zeppelin job submissions. Default capacity is 40, with a maximum capacity of 100. To allocate more of the cluster's resources to Notebook, increase this queue's capacity.
-
default: Queue used for all Hive and Spark Thrift job submissions. Default capacity is 10, with a maximum capacity of 100.
You can modify existing queues, or add new ones. To create a new queue, see Create Work Queues. Total capacity of all queues cannot exceed 100%.