Skip to main content
Version: FCP 25.11

Cluster Quotas

You can set quota limits for clusters by user/group, including maximum CPU, maximum GPU, maximum memory, and maximum number of running jobs.

Limits​

  • Administrators can configure quotas for all clusters. Regular users can configure quotas only for clusters they created or clusters shared with them with read/write permission.
  • When binding groups, administrators can select groups in the environment; regular users can only type group names (same interaction as access control). Quotas take effect based on a user's primary group.
  • Upgrade note: If quotas were managed via SOP before version 23.12, and you want to use the product quota feature afterwards, delete old quota entries first to avoid conflicts.

Quota behavior​

  • Quotas can be configured only when per-user resource restriction is enabled. When you click Add quota, the system checks whether per-user resource restriction is enabled for the cluster:
    • If disabled, the top-right shows a prompt: "Please enable per-user resource restriction first."
    • If enabled, you enter the Add Quota page.
  • Quotas are supported only for groups. A user's quota is determined by the user's primary group. Example:
    • User zhucui belongs to groups zhucui, defaultGroup, and group-1, with zhucui as the primary group. If quotas are set for defaultGroup and group-1 only, then zhucui has no quota and cannot submit jobs by default.
    • Quotas apply per user. Setting a quota for a primary group means each user whose primary group is that group has the quota. For example, if zhucui and test have primary group group and the quota for group is CPU=10, then each user can use 10 CPUs (they do not share a single 10-CPU pool).
  • If user-group relationships are modified in system management, quotas take effect accordingly.

Per-user resource restriction​

When per-user resource restriction is enabled, all users cannot submit jobs by default. You must add cluster quotas to grant resources. When it is disabled, configured quotas no longer take effect and users are not limited by cluster quotas by default. You can configure this when creating a cluster or creating a template.

You can modify per-user resource restriction in the cluster overview.

  • When enabling: a confirmation prompt appears explaining that users cannot submit jobs by default and running jobs may be affected; perform this operation when the cluster is idle. After enabling:
    • Users cannot submit jobs through the scheduler by default.
    • You can add cluster quotas.
  • When disabling: a confirmation prompt appears explaining that quotas will no longer take effect and running jobs may be affected; perform this operation when the cluster is idle. After disabling:
    • Users can submit jobs normally without cluster quota restriction.
    • Existing cluster quotas no longer take effect.

Add quota​

You can add quotas only when the cluster is Running/Updating and per-user resource restriction is enabled.

Parameters:

  • Primary group: Required. Multi-select supported. Admins can select existing groups; regular users can only type group names.
  • Partition: Required. Multi-select supported. Only compute partitions in Running/Updating status can be selected.
  • CPU quota: Required. Default 10. Integer. Min 0. Use -1 for unlimited.
  • GPU quota: Required. Default -1 (unlimited). Integer. Min 0. Use -1 for unlimited.
  • Running job count: Required. Default 1000. Integer. Min 0. Use -1 for unlimited.

After you confirm:

  • A record is created for each group and partition pair, and each record has an auto-generated ID.
  • If the new quota conflicts with an existing record (same group + partition), an error is shown.
  • In Fsched cluster partitions, jobs submitted by users are constrained by quotas. Example: User user-1 has primary group group-1. If group-1 has CPU quota=1 on partition-1, and the user submits a job requesting 2 CPUs on partition-1, the job will stay queued even if the partition has more than 2 free CPUs.