You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.
extras:
gangAllocation: true/falsehivedscheduler:
jobPriorityClass: crit | prod | test (default) | oppotaskRoles:
<taskrole_name>:
pinnedCellId: string | null (default)# if resourcePerInstance doesn't exist, we should calculate it from # config.taskroles.<taskrole_name>.resourcePerInstance, and use null as skuTyperesourcePerInstance:
skuNum: number skuType: string | null (default)withinOne: string | null (default)taskRoleGroups:
# we don't allow single group: length of taskRoles must be > 1 # we don't allow overlap
- taskRoles: [master, worker]withinOne: string | null
Remaining question:
will extras.gangAllocation have any effect? - use the same behavior as before
should we modify api/v2/cluster/sku-types - should provide a new api which returns all cell chain
IgnoreK8sSuggestedNodes?
The text was updated successfully, but these errors were encountered:
new schema in OpenPAI job protocol:
Remaining question:
extras.gangAllocation
have any effect? - use the same behavior as beforeIgnoreK8sSuggestedNodes
?The text was updated successfully, but these errors were encountered: