Cloudera Docs

Directing user-specific workloads to dedicated YARN queues

Route unassigned user applications to dedicated YARN queues by using placement rules in the YARN Queue Manager UI.

In multi-tenant setups, jobs submitted by specific users or service accounts often lack an explicitly defined target queue. By default, these unassigned applications are assigned to root.default, which can lead to resource contention and SLA degradation.

Configure placement rules in the YARN Queue Manager UI to automatically route applications submitted by designated users or service accounts to specific, pre-configured YARN queues.

  • Ensure access to Cloudera Manager with administrative or queue management privileges.
  • Target YARN queue(s), such as root.prod.analytics or root.users.<username> must already be created and configured with the required resource allocations.
  1. Login to the Cloudera Manager Admin Console.
  2. Navigate to Clusters > YARN Queue Manager UI.
  3. Select the Placement Rules tab.
  4. Click + Add or Add Rule.
  5. Specify the parameters in the placement rule configuration dialog box.
    For example, the rule must match The submitting user's name and must run on root.default.yarn queue. For more information on configuration details, see creating placement rules.
  6. Click Add or Save.
  7. Click Save Changes and enter a commit message to deploy the configuration.
After configuring and deploying the placement rules, verify that applications are correctly routed to their assigned YARN queues. Follow these steps to test and validate your configuration:
  1. Submit a test job such as Spark shell or a Hive query under the target user account without specifying the --queue or mapreduce.job.queuename parameter.
  2. In Cloudera Manager, navigate to YARN > Applications or open the YARN ResourceManager Web UI.
  3. Verify that the application was assigned to the configured dedicated queue rather than root.default.