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
func (i *storeIndex) deleteKeyFromIndex(key, indexValue string, index Index) {
set := index[indexValue]
if set == nil {
return
}
set.Delete(key)
// If we don't delete the set when zero, indices with high cardinality
// short lived resources can cause memory to increase over time from
// unused empty sets. See `kubernetes/kubernetes/issues/84959`.
if len(set) == 0 {
delete(index, indexValue)
}
}
Describe the bug
indexSet should also be deleted if it is empty; otherwise, a lot of untouchable HashSets will cause memory leaks.
The client-go fix is kubernetes/kubernetes#84959
A proper fix would be:
Client Version
15.0.1
Kubernetes Version
1.19.3
Java Version
Java 8
To Reproduce
Memory grows higher after items are created and removed.
Expected behavior
no memory leak after item is removed.
KubeConfig
If applicable, add a KubeConfig file with secrets redacted.
Server (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: