Kinga Marton created YUNIKORN-433:
-------------------------------------
Summary: Extend configwatcher expiration time when a new request
comes in
Key: YUNIKORN-433
URL: https://issues.apache.org/jira/browse/YUNIKORN-433
Project: Apache YuniKorn
Issue Type: Bug
Reporter: Kinga Marton
Assignee: Kinga Marton
When two configuration reloading is triggered closely to each other it might
happen that, before the update is available the watcher times out, because it
is already running, since it was triggered during the first update/configmap
creation. Then the update triggers it again, the expiration time is not
modified. Everything is about the timing: if you wait with the update until
the first triggered configwatcher times out, then the changes will be synced.
Also it works if you are quick enough with the update and the changes takes
effect before the expire time.
For avoiding this kind of issues with the config changes we need to add 2
changes:
* increase the timeout for the configwatcher
* restart the configwatcher timer when the configwatcher is triggered and
theer is already one running.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
