Kinga Marton created YUNIKORN-404:
-------------------------------------
Summary: During config update queue is removed without any reason
Key: YUNIKORN-404
URL: https://issues.apache.org/jira/browse/YUNIKORN-404
Project: Apache YuniKorn
Issue Type: Bug
Components: core - cache
Reporter: Kinga Marton
While updating the configuration there are cases when queues are removed
without any reason.
Steps to reproduce: start YK with the following configuration:
{code:yaml}
configuration: |
partitions:
-
name: default
queues:
-
name: root
submitacl: '*'
queues:
-
name: someQueue
resources:
guaranteed:
memory: 50000
vcore: 5000
max:
memory: 80000
vcore: 8000{code}
Update the configuration to the following one:
{code:yaml}
partitions:
-
name: default
queues:
-
name: root
properties:
application.sort.policy: stateaware
submitacl: '*'
queues:
- name: a
queues:
- name: b
queues:
- name: c
- name: X
queues:
- name: riskteam
resources:
guaranteed:
gpu: "0"
memory: "256"
vcore: "1"
max:
gpu: "0"
memory: "512"
vcore: "2"
placementrules:
- name: tag
create: true
value: namespace{code}
*Expected result*: someQueue should be deleted, a.b.c. and X.riskteam should be
created
*Actual result:* someQueue is deleted, a.b.c is created, X.riskteam is created
and right after then is is marked for removal.
*Note:* is happening both through API and with direct configmap update
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
