Ayub Pathan created YUNIKORN-334:
------------------------------------

             Summary: Configmap updates are not consumed and updated for queues
                 Key: YUNIKORN-334
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-334
             Project: Apache YuniKorn
          Issue Type: Bug
          Components: core - scheduler
            Reporter: Ayub Pathan


Update configmap with new property(for example: stateaware app sorting or 
viceversa) and applied to the queues correctly

* Apply the below config
{noformat}
kubectl describe configmaps -n yunikorn yunikorn-configs
Name:         yunikorn-configs
Namespace:    yunikorn
Labels:       app=yunikorn
              chart=yunikorn-0.9.0
              heritage=Helm
              release=yunikorn
Annotations:  helm.sh/hook: pre-install
              helm.sh/hook-weight: 2

Data
====
queues.yaml:
----
partitions:
  -
    name: default
    placementrules:
      - name: tag
        value: namespace
        create: true
    queues:
      - name: root
        submitacl: '*'

Events:  <none>
{noformat}

* kubectl create namespace dev7
* Create an app under this queue
{noformat}
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: sleep-157
    applicationId: sleep-157
  name: sleep-157-2
  namespace: dev7
spec:
  schedulerName: yunikorn
  restartPolicy: Never
  containers:
    - name: sleep-60s-1
      image: "alpine:latest"
      command: ["sleep", "60"]
      resources:
        requests:
          cpu: "300m"
          memory: "300M"
{noformat}

* VErify the queues API response.
{noformat}
{
        queuename: "dev7",
        status: "Active",
        capacities: {
                capacity: "[]",
                maxcapacity: "[]",
                usedcapacity: "[memory:300 vcore:300]",
                absusedcapacity: "[]"
        },
        queues: null,
        properties: {
                application.sort.policy: "stateaware"
        }
}
{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to