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.

If preemption was set to Off (disabled), the following queues are available by default:

• 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.

If preemption was set to On (enabled), the following queues are available by default:

• 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%.

To manage work queue capacity:

1. Open the cluster console for the cluster. See Access the Big Data Cloud Console.
2. Click Settings.

   The Queues tab on the Settings page is displayed, listing the current queues and their configurations. For information about the details on the page, see Big Data Cloud Console: Settings Page.

3. Modify queue capacity as desired, making note of the explanatory information on the page. Preemption was set when the cluster was created and cannot be changed.