github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 22:46:12 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #86919 from ahg-g/ahg-fix

Browse Source 
Fix how we check for node info list consistency
This commit is contained in:
Kubernetes Prow Robot 2020-01-07 14:09:05 -08:00 committed by GitHub
commit 6099a739d8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pkg/scheduler/internal/cache/cache.go vendored
View File

@ -261,12 +261,12 @@ func (cache *schedulerCache) UpdateNodeInfoSnapshot(nodeSnapshot *nodeinfosnapsh
cache.updateNodeInfoSnapshotList(nodeSnapshot, updateAllLists) cache.updateNodeInfoSnapshotList(nodeSnapshot, updateAllLists)
} }
if len(nodeSnapshot.NodeInfoList) != len(nodeSnapshot.NodeInfoMap) { if len(nodeSnapshot.NodeInfoList) != cache.nodeTree.numNodes {
errMsg := fmt.Sprintf("snapshot state is not consistent, length of NodeInfoList=%v not equal to length of NodeInfoMap=%v "+ errMsg := fmt.Sprintf("snapshot state is not consistent, length of NodeInfoList=%v not equal to length of nodes in tree=%v "+
"length of nodes in cache=%v, length of nodes in tree=%v"+ ", length of NodeInfoMap=%v, length of nodes in cache=%v"+
", trying to recover", ", trying to recover",
len(nodeSnapshot.NodeInfoList), len(nodeSnapshot.NodeInfoMap), len(nodeSnapshot.NodeInfoList), cache.nodeTree.numNodes,
len(cache.nodes), cache.nodeTree.numNodes) len(nodeSnapshot.NodeInfoMap), len(cache.nodes))
klog.Error(errMsg) klog.Error(errMsg)
// We will try to recover by re-creating the lists for the next scheduling cycle, but still return an // We will try to recover by re-creating the lists for the next scheduling cycle, but still return an
// error to surface the problem, the error will likely cause a failure to the current scheduling cycle. // error to surface the problem, the error will likely cause a failure to the current scheduling cycle.