Benjamin Teke created YARN-11533:
------------------------------------

             Summary: CapacityScheduler CapacityConfigType changed in legacy 
queue allocation mode
                 Key: YARN-11533
                 URL: https://issues.apache.org/jira/browse/YARN-11533
             Project: Hadoop YARN
          Issue Type: Bug
          Components: capacity scheduler
    Affects Versions: 3.4.0
            Reporter: Benjamin Teke
            Assignee: Benjamin Teke


YARN-11000 changed the CapacityConfigType determination method in legacy queue 
mode, which has some undesired effects, like marking root to be in percentage 
mode, when the rest of the queue structure is in absolute.

Config:

{code:java}
<configuration>
        <property>
                <name>yarn.scheduler.capacity.root.maximum-capacity</name>
                <value>[memory=40960,vcores=32]</value>
        </property>
        <property>
                <name>yarn.scheduler.capacity.root.queues</name>
                <value>default</value>
        </property>
        <property>
                <name>yarn.scheduler.capacity.root.capacity</name>
                <value>[memory=40960,vcores=32]</value>
        </property>
        <property>
                
<name>yarn.scheduler.capacity.schedule-asynchronously.enable</name>
                <value>true</value>
        </property>
        <property>
                
<name>yarn.scheduler.capacity.root.default.maximum-capacity</name>
                <value>[memory=40960,vcores=32]</value>
        </property>
        <property>
                
<name>yarn.scheduler.capacity.root.default.maximum-am-resource-percent</name>
                <value>0.2</value>
        </property>
        <property>
                <name>yarn.scheduler.capacity.root.default.capacity</name>
                <value>[memory=40960,vcores=32]</value>
        </property>
</configuration>
{code}

Old response:

{code:java}
{
    "scheduler": {
        "schedulerInfo": {
            "type": "capacityScheduler",
            "capacity": 100.0,
            "usedCapacity": 0.0,
            "maxCapacity": 100.0,
            "weight": -1.0,
            "normalizedWeight": 0.0,
            "queueName": "root",
            "queuePath": "root",
            "maxParallelApps": 2147483647,
            "isAbsoluteResource": true,
            "queues": {...}
            "queuePriority": 0,
            "orderingPolicyInfo": "utilization",
            "mode": "absolute",
            "queueType": "parent",
            "creationMethod": "static",
            "autoCreationEligibility": "off",
            "autoQueueTemplateProperties": {},
            "autoQueueParentTemplateProperties": {},
            "autoQueueLeafTemplateProperties": {}
        }
    }
}
{code}

New response:

{code:java}
{
    "scheduler": {
        "schedulerInfo": {
            "type": "capacityScheduler",
            "capacity": 100.0,
            "usedCapacity": 0.0,
            "maxCapacity": 100.0,
            "weight": -1.0,
            "normalizedWeight": 0.0,
            "queueName": "root",
            "queuePath": "root",
            "maxParallelApps": 2147483647,
            "isAbsoluteResource": false,
            "queues": {...}
            "queuePriority": 0,
            "orderingPolicyInfo": "utilization",
            "mode": "percentage",
            "queueType": "parent",
            "creationMethod": "static",
            "autoCreationEligibility": "off",
            "autoQueueTemplateProperties": {},
            "autoQueueParentTemplateProperties": {},
            "autoQueueLeafTemplateProperties": {}
        }
    }
}
{code}

This is misleading and has some side-effects on various clients.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to