Configuring a Queue

Scenario

The administrator can modify queue configuration of a specific tenant on FusionInsight Manager based on service requirements.

Prerequisites

Tenants who use the Superior scheduler have been added.

Procedure

1. On FusionInsight Manager, click Tenant Resources.
2. Click the Dynamic Resource Plan tab.
3. Click the Queue Configuration tab.
4. Set Cluster to the name of the cluster to be operated. In the tenant queue table, click Modify in the Operation column of the specific tenant queue.
   

   • You can also open the queue modification page as follows: Click the target tenant in the tenant list on the left of the Tenant Resources Management tab page. In the window that is displayed, click Resource. On the page that is displayed, click behind Queue Configuration (queue name).
   • One queue can be bound to only one non-default resource pool.
   • For parameters such as Max Allocated vCores, Max Allocated Memory(MB), Max Running Apps, Max Running Apps per User and Max Pending Apps, if the sub-tenant value is -1, the parent tenant value can be set to a specific limit. If the parent tenant value is a specific limit, the sub-tenant value can be set to -1.
   • The values of Max Allocated vCores and Max Allocated Memory(MB) must be changed to values other than -1 for the modification to take effect.

   Table 1 Queue configuration parameters

   Parameter	Description
   Max Master Shares(%)	Indicates the maximum percentage of resources occupied by all ApplicationMasters in the current queue.
   Max Allocated vCores	Indicates the maximum number of cores allocated to a Yarn container in the current queue. The default value is -1, indicating that the value range is not limited.
   Max Allocated Memory(MB)	Indicates the maximum memory allocated to a Yarn container in the current queue. The default value is -1, indicating that the value range is not limited.
   Max Running Apps	Indicates the maximum number of tasks supported by the current queue at one time. The default value is -1, which indicates that the number of tasks that can be executed concurrently in the queue is not restricted (same meaning as the parameter value left blank). Value 0 indicates that no task can be executed. The value ranges from -1 to 2147483647.
   Max Running Apps per User	Indicates the maximum number of tasks allowed for a user in the current queue at one time. The default value is -1, which indicates that the number of tasks that can be executed concurrently in the queue is not restricted (same meaning as the parameter value left blank). Value 0 indicates that no task can be executed. The value ranges from -1 to 2147483647.
   Max Pending Apps	Indicates the maximum number of tasks that can be suspended in the current queue at one time. The default value is -1, which indicates that the number of tasks that can be suspended concurrently in the queue is not restricted (same meaning as the parameter value left blank). Value 0 indicates that no task can be suspended. The value ranges from -1 to 2147483647.
   Resource Allocation Rule	Indicates the rule for allocating resources to different tasks of a user. The rule can be FIFO or FAIR. If a user submits multiple tasks in the current queue and the rule is FIFO, the tasks are executed one by one in sequential order; if the rule is FAIR, resources are evenly allocated to all tasks.
   Default Resource Label	Indicates that tasks are executed on a node with a specified resource label.
   Active	ACTIVE: indicates that the current queue can receive and execute tasks. INACTIVE: indicates that the current queue can receive but cannot execute tasks. Tasks submitted to the queue are suspended.
   Open	OPEN: indicates that the current queue is opened. CLOSED: indicates that the current queue is closed. Tasks submitted to the queue are rejected.
   Migrate Queue Upon Fault	If multi-az availability is enabled for the cluster and an AZ is faulty, set Migrate Queue Upon Fault to TRUE to submit running queues of the tenant to other AZs.

5. Click OK. The queue configuration is complete.