![]() The evictorLock only protects zonePodEvictor and zoneNoExecuteTainter. processTaintBaseEviction showed indications of increased lock contention among goroutines (see issue 110341 for more details). The refactor done is to ensure that all codepaths in that function that hold the evictorLock AND make API calls under the lock, are now making API calls outside the lock and the lock is held only for accessing either zonePodEvictor or zoneNoExecuteTainter or both. Two other places where the refactor was done is the doEvictionPass and doNoExecuteTaintingPass functions which make multiple API calls under the evictorLock. Signed-off-by: Madhav Jivrajani <madhav.jiv@gmail.com> |
||
---|---|---|
.. | ||
config | ||
scheduler | ||
metrics.go | ||
node_lifecycle_controller_test.go | ||
node_lifecycle_controller.go | ||
OWNERS |