You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nfd-master: fix memory leak when leader election is enabled
Fix a serious memory leak of non-leaders that was caused by bad chan
usage. With leader election enabled, the nfdAPIUpdateHandler() was
not started for non-leader instances, and thus, there was no reader for
the chans that the nfdController uses to communicate what objects to
update. This, in turn caused blocking in the kubernetes API informer
context (trying to queue data into the chan), piling up requests on each
NodeFeature update, consuming more and more memory (that would not be
released unless we became the leader).
(cherry picked from commit a595439)
0 commit comments