github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Avoid dumping all information in large clusters

Browse Source
This commit is contained in:
Wojciech Tyczynski
2016-05-24 09:59:13 +02:00
parent 8f104a7b0f
commit bd920de4a4
1 changed files with 15 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
test/e2e/framework/util.go
View File

@@ -2264,9 +2264,21 @@ func DumpAllNamespaceInfo(c *client.Client, namespace string) {
// that if you delete a bunch of pods right before ending your test, // that if you delete a bunch of pods right before ending your test,
// you may or may not see the killing/deletion/Cleanup events. // you may or may not see the killing/deletion/Cleanup events.
dumpAllPodInfo(c) // If cluster is large, then the following logs are basically useless, because:
// 1. it takes tens of minutes or hours to grab all of them
dumpAllNodeInfo(c) // 2. there are so many of them that working with them are mostly impossible
// So we dump them only if the cluster is relatively small.
maxNodesForDump := 20
if nodes, err := c.Nodes().List(api.ListOptions{}); err == nil {
if len(nodes.Items) <= maxNodesForDump {
dumpAllPodInfo(c)
dumpAllNodeInfo(c)
} else {
Logf("skipping dumping cluster info - cluster too large")
}
} else {
Logf("unable to fetch node list: %v", err)
}
} }
// byFirstTimestamp sorts a slice of events by first timestamp, using their involvedObject's name as a tie breaker. // byFirstTimestamp sorts a slice of events by first timestamp, using their involvedObject's name as a tie breaker.